CVE-2026-99615: Linux kernel · l2tp: only return sessions of the given tunnel in l2tp_session_get()
Source GCVE Database
Not known to be exploited · fixed in a75facf4bb3e866103ddca4f47a6f3ca4b090d8b : update Linux kernel when convenient.
Data as of 20 Nov 2026, 07:34 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in a75facf4bb3e866103ddca4f47a6f3ca4b090d8b, 649d00a0e1ff2f5a4f5b8c194755f9b9bbd98504, 26cb789c98bdd4dcc2af6e083eeaa23c4d8715c4 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade Linux kernel to a75facf4bb3e866103ddca4f47a6f3ca4b090d8b, 649d00a0e1ff2f5a4f5b8c194755f9b9bbd98504, 26cb789c98bdd4dcc2af6e083eeaa23c4d8715c4 or 2dec8c5a6928f27a40e8880df2af3289693abbcd.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: l2tp: only return sessions of the given tunnel in l2tp_session_get() Commit 5f77c18ea556 ("l2tp: use IDR for all session lookups") made pppol2tp_connect() and the netlink session commands find sessions with l2tp_session_get(), passing the socket of the tunnel they name. L2TPv3 session IDs are unique per network namespace, except that sessions carried over UDP are only unique per UDP socket, the socket of their tunnel. However, l2tp_v3_session_get() only checks the socket when another session has the same session ID. Otherwise it returns the session, whichever tunnel it belongs to. As of now, a session command that names the wrong tunnel acts on a session of another tunnel, and a PPPoL2TP socket for a second L2TPv3 tunnel fails with EEXIST, because it finds session 0 of the first tunnel. The issue can be reproduced with: ip l2tp add tunnel tunnel_id 3 peer_tunnel_id 3 encap udp \ local 127.0.0.1 remote 127.0.0.1 udp_sport 5003 udp_dport 6003 ip l2tp add tunnel tunnel_id 4 peer_tunnel_id 4 encap udp \ local 127.0.0.1 remote 127.0.0.1 udp_sport 5004 udp_dport 6004 ip l2tp add session tunnel_id 3 session_id 7 peer_session_id 7 ip l2tp del session tunnel_id 4 session_id 7 ip l2tp show session Before that commit, the delete fails with "No such device", and session 7 of tunnel 3 is still listed. After that commit, the delete succeeds, and session 7 of tunnel 3 is gone. This patch will make l2tp_session_get() return NULL when the L2TPv3 session it finds does not belong to the given socket. The receive path calls l2tp_v3_session_get() directly and is not changed.
References
- nvd.nist.gov/vuln/detail/CVE-2026-99615 (opens in a new tab)
- git.kernel.org/stable/c/26cb789c98bdd4dcc2af6e083eeaa23c4d8715c4 (opens in a new tab)
- git.kernel.org/stable/c/2dec8c5a6928f27a40e8880df2af3289693abbcd (opens in a new tab)
- git.kernel.org/stable/c/649d00a0e1ff2f5a4f5b8c194755f9b9bbd98504 (opens in a new tab)
- git.kernel.org/stable/c/a75facf4bb3e866103ddca4f47a6f3ca4b090d8b (opens in a new tab)