CVE-2026-80838

vxlan: keep the last remote linked during FDB flush

N/A
Published: September 4, 2026 at 03:54 PM UTC
Updated: October 19, 2026 at 09:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.7c499fccb71cb85902b5c5b9ce9c9ae6683e54a8f
Vendor states this is fixed in 2a7c2f00843225d5f037676bca649321f3d024c7 (fixed)
Vendor states this is fixed in 4bbc76ee1b21d3bd045d6d819b2bacd30a6372ab (fixed)
Vendor states this is fixed in 8ba68fd6cdd1e3c92b92f25c7e48bf7bd51a183c (fixed)
Vendor states this is fixed in a8820c8a7718327e96849782033e7c85a0f6bcfe (fixed)
Vendor states this is fixed in d5d4a7b538b52db63927773a8905fcd9f78a42e2 (fixed)
Vendor states this is fixed in 6.12.108 (unaffected)
Vendor states this is fixed in 6.18.49 (unaffected)
Vendor states this is fixed in 6.7 (unaffected)
Vendor states this is fixed in 7.1.13 (unaffected)
Vendor states this is fixed in 7.2.3 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card