CVE-2026-80996: Linux kernel · net: l2tp: do not propagate multicast notification errors
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in af20e269f7459d2ce69887fdf2fad7caf986c865 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:07 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in af20e269f7459d2ce69887fdf2fad7caf986c865, 50c4038f1670bf9a80c6a58ae83d1602decd8481, 9c340473f4822bb31b151c19afd17448eda5acd1 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 11 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
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
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: net: l2tp: do not propagate multicast notification errors The tunnel create, tunnel modify, session create, and session modify netlink handlers send multicast notifications through helpers that can fail while allocating or encoding a message, or while multicasting it. For tunnel and session create/modify, a notification is sent after the live operation has completed. Returning a best-effort notification error as the command result can therefore report failure for an operation that already committed and can cause callers to retry and accumulate live objects. Keep sending notifications for listener visibility, but do not propagate their best-effort status as the command result. This also keeps the tunnel modify command consistent with the other notification-only paths.
References
- git.kernel.org/stable/c/7efe1c31e0903a5aa796feb96d3adab574b7ff41 (opens in a new tab)
- git.kernel.org/stable/c/0fe037d5eaad938aa3e9143ee071aa237750b42b (opens in a new tab)
- git.kernel.org/stable/c/9c340473f4822bb31b151c19afd17448eda5acd1 (opens in a new tab)
- git.kernel.org/stable/c/50c4038f1670bf9a80c6a58ae83d1602decd8481 (opens in a new tab)
- git.kernel.org/stable/c/af20e269f7459d2ce69887fdf2fad7caf986c865 (opens in a new tab)