CVE-2026-64119

In the Linux kernel, the following vulnerability has been resolved: l2tp: use list_del_rcu in l2tp_session_unhash An unprivileged local user can pin a host CPU indefinitely in l2tp_session_get_by_ifname() by issuing L2TP_CMD_SESSION_GET on L2TP_ATTR_IFNAME concurrently with L2TP_CMD_SESSION_CREATE and L2TP_CMD_SESSION_DELETE on the same tunnel. All three commands take GENL_UNS_ADMIN_PERM, so CAP_NET_ADMIN in the netns user namespace suffices; on any host that has l2tp_core loaded the trigger is reachable from a standard `unshare -Urn` sandbox. l2tp_session_unhash() removes a session from tunnel->session_list with list_del_init(), but that list is walked by l2tp_session_get_by_ifname() with list_for_each_entry_rcu() under rcu_read_lock_bh(). list_del_init() leaves the deleted entry's next/prev self-pointing; a reader that has loaded the entry and then advances pos->list.next reads &session->list, container_of()s back to the same session, and list_for_each_entry_rcu() never reaches the list head. The CPU stays in strcmp() inside the walker, with BH and preemption disabled, so RCU grace periods on the host stall behind it and the wedged thread cannot be killed (SIGKILL is delivered on syscall return). Use list_del_rcu() to match the existing list_add_rcu() in l2tp_session_register(); the deleted session remains visible to in-flight walkers with consistent next/prev pointers until kfree_rcu() in l2tp_session_free() releases it. tunnel->session_list has exactly one list_del_init() call site; the list_del_init (&session->clist) at l2tp_core.c:533 operates on the per-collision list, which is not walked under RCU. list_empty(&session->list) is not used anywhere in net/l2tp/ after the unhash point, so dropping the post-delete self-init is safe; the fix has no userspace-visible behavior change.

• https://git.kernel.org/stable/c/5e40919a40cb3e590ed45c2a54a4a2518aa88a99
• https://git.kernel.org/stable/c/979c017803c40829b03acd9e5236e354b7622360
• https://git.kernel.org/stable/c/acab6314bb75be994f720ed13e9d9139cbf828a8
• https://git.kernel.org/stable/c/e0c3dd7b30cc5ee42ab502da140cda93d794a20b

Published

Jul 19, 2026

Last Modified

Jul 30, 2026

Status

Awaiting Analysis

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-64113In the Linux kernel, the following vulnerability has been re…9.8
• CVE-2026-64114In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-64115In the Linux kernel, the following vulnerability has been re…8.8
• CVE-2026-64116In the Linux kernel, the following vulnerability has been re…7.5
• CVE-2026-64117In the Linux kernel, the following vulnerability has been re…8.8
• CVE-2026-64118In the Linux kernel, the following vulnerability has been re…8.4
• CVE-2026-6412Certificate policy and RFC 8446 compliance concerns regardin…4.3
• CVE-2026-64120In the Linux kernel, the following vulnerability has been re…
• CVE-2026-64121In the Linux kernel, the following vulnerability has been re…
• CVE-2026-64122In the Linux kernel, the following vulnerability has been re…9.8
• CVE-2026-64123In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-64124In the Linux kernel, the following vulnerability has been re…8.8