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-80838vxlan: keep the last remote linked during FDB flush

Description

In the Linux kernel, the following vulnerability has been resolved: vxlan: keep the last remote linked during FDB flush A non-nexthop FDB entry is expected to have at least one remote while it remains reachable through the FDB hash table. A filtered bulk flush violates this invariant when every remote matches: It unlinks the last remote in vxlan_fdb_dst_destroy() and only afterwards tells vxlan_flush() to destroy the parent FDB entry. An RCU reader can find the parent during this interval. first_remote_rcu() then applies list_entry_rcu() to the empty list head, producing an invalid remote pointer that the receive learning path can read from and write to. When a matching remote is the sole remaining remote, leave it linked and ask the caller to destroy the entire FDB entry. vxlan_fdb_destroy() keeps the remote attached while sending the deletion notification and removing the parent from the lookup structures.

Timeline

  1. ID reserved

    By Linux

  2. · 9 days later

    Published

  3. · 45 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.17% · top 94% 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 c499fccb71cb85902b5c5b9ce9c9ae6683e54a8f – < 2a7c2f00843225d5f037676bca649321f3d024c7
    • affected c499fccb71cb85902b5c5b9ce9c9ae6683e54a8f – < a8820c8a7718327e96849782033e7c85a0f6bcfe
    • affected c499fccb71cb85902b5c5b9ce9c9ae6683e54a8f – < 8ba68fd6cdd1e3c92b92f25c7e48bf7bd51a183c
    • affected c499fccb71cb85902b5c5b9ce9c9ae6683e54a8f – < 4bbc76ee1b21d3bd045d6d819b2bacd30a6372ab
    • affected c499fccb71cb85902b5c5b9ce9c9ae6683e54a8f – < d5d4a7b538b52db63927773a8905fcd9f78a42e2
  • Linux · Linux

    • affected 6.7
    • unaffected < 6.7
    • unaffected 6.12.108 – ≤ 6.12.*
    • unaffected 6.18.49 – ≤ 6.18.*
    • unaffected 7.1.13 – ≤ 7.1.*
    • unaffected 7.2.3 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .