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.
Published: 2026-09-04
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

In the Linux kernel's VXLAN implementation, a flaw in the handling of forwarding database (FDB) flushes allows a filtered bulk flush to unlink the last remote entry prematurely. During this period an RCU reader can access the now-empty list, producing an invalid pointer that the receive learning path may read from and write to. This mismanagement can corrupt kernel memory and may cause the system to crash, effectively creating a denial of service on a vulnerable host. The weakness corresponds to the classic use‑after‑free flaw (CWE‑416). No patch or workaround is provided in the advisory, so the impact is strictly limited to the kernel code paths that perform the flushing logic.

Affected Systems

The defect resides entirely in the Linux kernel; any distribution that ships the standard vxlan module before the commit that fixed this bug is affected. No specific version matrix is supplied, so all kernels that include the unpatched vxlan implementation are considered vulnerable. The issue is located in the vxlan_fdb_dst_destroy() and vxlan_flush() functions, which are part of the core networking stack.

Risk and Exploitability

The CVSS score is not specified in the advisory; the EPSS score is unavailable and the vulnerability is not listed in the CISA KEV catalog. Based on the description it is inferred that an attacker would need to deliver specially crafted VXLAN packets to trigger the faulty flush logic. If successful, the resulting kernel memory corruption could crash the system. Because the required conditions involve low‑level networking primitives and the bug is in kernel code, the likelihood of exploitation is moderate and it may be limited to environments that expose VXLAN interfaces to untrusted traffic.

Generated by OpenCVE AI on September 4, 2026 at 18:47 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the Linux kernel to a version that includes the commit that fixes the VXLAN FDB flush bug.
  • If a distro update is not yet available, manually apply the patch to the kernel source before building and installing a new kernel image.
  • As a temporary measure, restrict VXLAN traffic to trusted sources, or disable unused VXLAN interfaces until an official patch is deployed.

Generated by OpenCVE AI on September 4, 2026 at 18:47 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 04 Sep 2026 19:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-416

Fri, 04 Sep 2026 16:00:00 +0000

Type Values Removed Values Added
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.
Title vxlan: keep the last remote linked during FDB flush
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-09-04T15:54:48.371Z

Reserved: 2026-08-26T14:34:25.796Z

Link: CVE-2026-80838

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-04T16:18:12.183

Modified: 2026-09-04T16:18:12.183

Link: CVE-2026-80838

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-04T19:00:14Z

Weaknesses