Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-80996net: l2tp: do not propagate multicast notification errors

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.

Timeline

  1. ID reserved

    By Linux

  2. · 16 days later

    Published

  3. · 49 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 33f72e6f0c67f673fd0c63a8182dbd9ffb8cf50b – < 73761c3cfb6d86392d63335d10f464b9d43275a7
    • affected 33f72e6f0c67f673fd0c63a8182dbd9ffb8cf50b – < 7efe1c31e0903a5aa796feb96d3adab574b7ff41
    • affected 33f72e6f0c67f673fd0c63a8182dbd9ffb8cf50b – < 0fe037d5eaad938aa3e9143ee071aa237750b42b
    • affected 33f72e6f0c67f673fd0c63a8182dbd9ffb8cf50b – < 9c340473f4822bb31b151c19afd17448eda5acd1
    • affected 33f72e6f0c67f673fd0c63a8182dbd9ffb8cf50b – < 50c4038f1670bf9a80c6a58ae83d1602decd8481
    • affected 33f72e6f0c67f673fd0c63a8182dbd9ffb8cf50b – < af20e269f7459d2ce69887fdf2fad7caf986c865
  • Linux · Linux

    • affected 4.0
    • unaffected < 4.0
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80996 badge
[![CVE-2026-80996](https://cveledger.app/badge/CVE-2026-80996.svg)](https://cveledger.app/cve/CVE-2026-80996)

Record last updated .