CVE-2026-23120: l2tp: avoid one data-race in l2tp_tunnel_del_work()
In the Linux kernel, the following vulnerability has been resolved:
l2tp: avoid one data-race in l2tp_tunnel_del_work()
We should read sk->sk_socket only when dealing with kernel sockets.
syzbot reported the following data-race:
BUG: KCSAN: data-race in l2tp_tunnel_del_work / sk_common_release
write to 0xffff88811c182b20 of 8 bytes by task 5365 on cpu 0:
sk_set_socket include/net/sock.h:2092 [inline]
sock_orphan include/net/sock.h:2118 [inline]
sk_common_release+0xae/0x230 net/core/sock.c:4003
udp_lib_close+0x15/0x20 include/net/udp.h:325
inet_release+0xce/0xf0 net/ipv4/af_inet.c:437
__sock_release net/socket.c:662 [inline]
sock_close+0x6b/0x150 net/socket.c:1455
__fput+0x29b/0x650 fs/file_table.c:468
____fput+0x1c/0x30 fs/file_table.c:496
task_work_run+0x131/0x1a0 kernel/task_work.c:233
resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
__exit_to_user_mode_loop kernel/entry/common.c:44 [inline]
exit_to_user_mode_loop+0x1fe/0x740 kernel/entry/common.c:75
__exit_to_user_mode_prepare include/linux/irq-entry-common.h:226 [inline]
syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:256 [inline]
syscall_exit_to_user_mode_work include/linux/entry-common.h:159 [inline]
syscall_exit_to_user_mode include/linux/entry-common.h:194 [inline]
do_syscall_64+0x1e1/0x2b0 arch/x86/entry/syscall_64.c:100
entry_SYSCALL_64_after_hwframe+0x77/0x7f
read to 0xffff88811c182b20 of 8 bytes by task 827 on cpu 1:
l2tp_tunnel_del_work+0x2f/0x1a0 net/l2tp/l2tp_core.c:1418
process_one_work kernel/workqueue.c:3257 [inline]
process_scheduled_works+0x4ce/0x9d0 kernel/workqueue.c:3340
worker_thread+0x582/0x770 kernel/workqueue.c:3421
kthread+0x489/0x510 kernel/kthread.c:463
ret_from_fork+0x149/0x290 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246
value changed: 0xffff88811b818000 -> 0x0000000000000000
Security readout for executives and security teams
Plain-English summary
CVE-2026-23120 is a Linux kernel race condition in L2TP tunnel cleanup. The public record shows it was found by syzbot/KCSAN and fixed in stable kernel commits. No CVSS score, business impact, or active exploitation evidence is provided, so urgency depends on whether affected Linux kernels and L2TP functionality are present.
Executive priority
Do not treat this as an emergency based on current public evidence. Assign normal kernel patch management priority, with faster remediation for VPN or networking systems using L2TP because they are more likely to reach the affected code path.
Technical view
The issue is a data race between l2tp_tunnel_del_work() reading sk->sk_socket and socket release code clearing that pointer. The fix narrows sk->sk_socket reads to kernel-socket handling. Sources identify Linux kernel as affected across listed version/range markers and provide multiple stable backport commits, but do not describe exploitability or attacker prerequisites.
Likely exposure
Exposure is likely limited to systems running affected Linux kernels where the L2TP kernel path can be exercised. VPN, networking, appliance, and hosting environments should check kernel versions and L2TP use. The provided data does not prove remote exposure or default exploitability.
Exploitation context
The source bundle shows syzbot reported a KCSAN data race. KEV is false, and no cited source claims active exploitation, public exploit availability, privilege requirements, or practical attack impact. Treat exploitation status as unconfirmed.
Researcher notes
The record provides a concrete race trace and stable commit references but no CVSS, CWE, exploitability analysis, or impact statement. Researchers should focus on reproducing version exposure and understanding whether local L2TP operations can trigger meaningful denial-of-service or memory-safety outcomes.
Mitigation direction
Inventory Linux kernel versions on affected assets.
Check vendor advisories for kernels containing the referenced stable commits.
Prioritize updates for systems using L2TP or VPN networking roles.
Disable unused L2TP functionality where operationally safe.
Monitor distribution security channels for severity and package guidance.
Validation and detection
Confirm deployed kernel versions against vendor fixed builds.
Verify whether L2TP modules or services are enabled.
Review kernel package changelogs for CVE-2026-23120 or referenced commits.
Track whether scanners recognize this CVE after vendor metadata updates.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-23120 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
8Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 14, 2026, 15:09 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.