CVE-2026-80838: vxlan: keep the last remote linked during FDB flush
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Fixed version: Linux Linux 2a7c2f00843225d5f037676bca649321f3d024c7, 4bbc76ee1b21d3bd045d6d819b2bacd30a6372ab, 8ba68fd6cdd1e3c92b92f25c7e48bf7bd51a183c.
Low priority for now. Upgrade to Linux Linux 2a7c2f00843225d5f037676bca649321f3d024c7, 4bbc76ee1b21d3bd045d6d819b2bacd30a6372ab, 8ba68fd6cdd1e3c92b92f25c7e48bf7bd51a183c or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 4, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.7affected
- c499fccb71cb85902b5c5b9ce9c9ae6683e54a8f and later · before 2a7c2f00843225d5f037676bca649321f3d024c7affected · git
- c499fccb71cb85902b5c5b9ce9c9ae6683e54a8f and later · before a8820c8a7718327e96849782033e7c85a0f6bcfeaffected · git
- c499fccb71cb85902b5c5b9ce9c9ae6683e54a8f and later · before 8ba68fd6cdd1e3c92b92f25c7e48bf7bd51a183caffected · git
- c499fccb71cb85902b5c5b9ce9c9ae6683e54a8f and later · before 4bbc76ee1b21d3bd045d6d819b2bacd30a6372abaffected · git
- c499fccb71cb85902b5c5b9ce9c9ae6683e54a8f and later · before d5d4a7b538b52db63927773a8905fcd9f78a42e2affected · git
- before 6.7not affected · semver
- 6.12.108 and later · up to and including 6.12.*not affected · semver
- 6.18.49 and later · up to and including 6.18.*not affected · semver
- 7.1.13 and later · up to and including 7.1.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.1.13-1 | 7.1.13-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80836Sep 4, 2026 · crypto: virtio - bound the akcipher result length0Monitor
- ← EarlierCVE-2026-80837Sep 4, 2026 · netfilter: nf_tables: don't queue packet path object notifications0Monitor
- Later →CVE-2026-80839Sep 4, 2026 · batman-adv: reject unrepresentable multicast TVLV offsets0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2a7c2f00843225d5f037676bca649321f3d024c7 | Vendor (CNA) |
| Linux Linux | 4bbc76ee1b21d3bd045d6d819b2bacd30a6372ab | Vendor (CNA) |
| Linux Linux | 8ba68fd6cdd1e3c92b92f25c7e48bf7bd51a183c | Vendor (CNA) |
| Linux Linux | a8820c8a7718327e96849782033e7c85a0f6bcfe | Vendor (CNA) |
| Linux Linux | d5d4a7b538b52db63927773a8905fcd9f78a42e2 | Vendor (CNA) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.