Skip to main content
Vulnerability Database/CVE-2026-98023

CVE-2026-98023: Linux Kernel VXLAN Race Condition Vulnerability

CVE-2026-98023 is a race condition flaw in Linux kernel VXLAN affecting dynamic FDB entries with nexthop IDs, causing list corruption. This post covers technical details, affected versions, impact, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-98023 Overview

CVE-2026-98023 is a use-after-free vulnerability in the Linux kernel VXLAN driver. The flaw allows list corruption and slab use-after-free in vxlan_fdb_destroy when dynamic forwarding database (FDB) entries reference a nexthop identifier. The VXLAN driver failed to reject dynamic FDB entries pointing to FDB nexthops, enabling a race between the aging timer running in softirq context and concurrent additions or deletions from a second VXLAN device sharing the same nexthop list.

Critical Impact

A local user with network configuration privileges can trigger kernel memory corruption, leading to denial of service or potential local privilege escalation on affected Linux systems.

Affected Products

  • Linux kernel versions containing the VXLAN FDB nexthop support commit referenced in the fix
  • Linux distributions shipping affected mainline kernels (specific versions unavailable in the advisory)
  • Systems using VXLAN overlays with FDB nexthop groups (for example, E-VPN deployments)

Discovery Timeline

  • 2026-09-25 - CVE-2026-98023 published to NVD
  • 2026-09-25 - Last updated in NVD database

Technical Details for CVE-2026-98023

Vulnerability Analysis

The VXLAN driver permits FDB entries to point to FDB nexthops so overlay traffic can load-balance across multiple VXLAN Tunnel Endpoints (VTEPs). These entries are intended for user-space control planes such as Ethernet VPN (E-VPN) where data-plane learning is disabled. They cannot be learned and cannot roam.

Despite this design, the driver did not block configuration of such entries with the dynamic flag. Dynamic entries are subject to aging, which runs in softirq context without the Routing Netlink (RTNL) lock. The per-nexthop FDB list is protected only by a per-device hash lock. When two VXLAN devices reference the same FDB nexthop, they share the list but synchronize on different locks.

This gap triggers a race during aging. One device can delete an entry while the other adds or removes an entry concurrently, producing list_del corruption warnings and a KASAN slab-use-after-free report in vxlan_fdb_destroy.

Root Cause

The root cause is missing input validation combined with insufficient locking. The driver accepted a configuration combination that violates its own invariants: dynamic entries referencing nexthop groups. Because aging runs without RTNL, mutations from different devices on a shared per-nexthop list are not serialized, allowing list pointers to become stale and reference freed memory.

Attack Vector

Exploitation requires local privileges sufficient to configure VXLAN interfaces, typically CAP_NET_ADMIN. An attacker creates two VXLAN devices pointing to the same FDB nexthop, then installs dynamic FDB entries. The kernel aging timer running in softirq triggers concurrent list operations, corrupting the shared list and producing a use-after-free in vxlan_fdb_destroy. The result is kernel memory corruption that can be used for denial of service and, under favorable heap conditions, local privilege escalation.

No verified public proof-of-concept code is available. Technical details are visible in the upstream kernel patches referenced below.

Detection Methods for CVE-2026-98023

Indicators of Compromise

  • Kernel log entries containing list_del corruption. next->prev should be followed by stack traces referencing vxlan_fdb_destroy, vxlan_cleanup, and run_timer_softirq.
  • KASAN reports showing BUG: KASAN: slab-use-after-free in vxlan_fdb_destroy.
  • Unexpected kernel panics or soft lockups on hosts running VXLAN overlays with FDB nexthop groups.

Detection Strategies

  • Audit bridge fdb configurations for dynamic entries that reference nexthop IDs on VXLAN devices.
  • Enumerate VXLAN devices sharing the same nexthop ID with ip nexthop show and correlate with FDB tables.
  • Enable KASAN on test and staging kernels to surface use-after-free conditions during VXLAN workload exercises.

Monitoring Recommendations

  • Forward kernel ring buffer messages to a centralized logging pipeline and alert on list_del corruption and KASAN strings.
  • Monitor host stability metrics (kernel oops counters, unexpected reboots) on nodes operating VXLAN overlays.
  • Track changes to VXLAN and nexthop configuration via netlink auditing to detect unauthorized dynamic entry creation.

How to Mitigate CVE-2026-98023

Immediate Actions Required

  • Apply the upstream kernel patches that reject dynamic FDB entries referencing FDB nexthop IDs.
  • Restrict CAP_NET_ADMIN to trusted administrators and workloads; avoid granting it to untrusted containers.
  • Audit existing VXLAN FDB entries and remove any dynamic entries that reference a nexthop ID before patching, since the kernel will reject them after update.

Patch Information

Upstream fixes are available in the following mainline and stable kernel commits:

The fix rejects the invalid configuration at creation and update time, ensuring the per-nexthop FDB list is mutated only under the RTNL lock. Kernel selftests were added to prevent regression.

Workarounds

  • Avoid configuring dynamic FDB entries that reference nexthop IDs on VXLAN devices until the patched kernel is deployed.
  • When using E-VPN or similar user-space control planes, ensure FDB entries referencing nexthops are installed as static entries only.
  • Where feasible, remove duplicate VXLAN devices sharing the same FDB nexthop ID to eliminate the cross-device race window.
bash
# Identify VXLAN FDB entries that reference nexthop IDs
bridge fdb show | grep -E 'nhid [0-9]+'

# List configured nexthop groups and their users
ip nexthop show

# Remove a problematic dynamic FDB entry (replace values accordingly)
bridge fdb del <MAC> dev vxlan0 nhid <ID>

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.