External risk intelligence

Linux Kernel VXLAN Torn Read Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 10.0)

CVE-2026-74475

This vulnerability exists within the Linux kernel VXLAN implementation, which manages low-level network tunneling protocols. It is an internal operating system component, not a user-facing application or service. It is not directly exposed to the public internet in normal deployments.

Halo Surface Signal: 1 out of 5 — much less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory addresses a vulnerability in the Linux kernel's network processing, specifically within the VXLAN component. The issue arises from how network hardware addresses are accessed, potentially leading to incorrect or incomplete data being read. While the immediate impact may be limited to specific internal operations, such kernel-level vulnerabilities can have broad implications for system stability and security if exploited. Confirming relevance and exposure is the primary concern.

  • Kernel network addresses read incorrectly.
  • Affects core operating system network functions.
  • Confirm relevance and system exposure.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by sending specially crafted network traffic. This traffic could reach the Linux kernel's VXLAN component, which handles network tunneling. If the kernel mishandles the hardware address data due to a race condition, it could lead to data corruption and manipulation.

  • Entry condition: Network access required.
  • Trigger point: Malformed network traffic.
  • Resulting risk: Data corruption and manipulation.

Live Threat

Current exploitation, exposure, and threat context

In the Linux kernel's VXLAN implementation, a vulnerability could allow for corrupted network traffic when the hardware address of a network neighbor is updated concurrently with its use in routing. This could occur when the kernel's networking subsystem is under heavy load or experiencing specific race conditions.

  • Network routing information could be corrupted.
  • Asynchronous updates to neighbor hardware addresses.
  • Potentially disrupts network connectivity.

Operational Fix

Recommended remediation, mitigation, and detection steps

This critical vulnerability resides within the Linux kernel's VXLAN networking implementation, impacting internal operating system functions rather than user-facing applications. Responsibility for addressing this typically falls to the infrastructure or platform teams managing the Linux environment. The immediate first step is to identify all Linux systems running the affected kernel version, determine their exposure and business criticality, and then coordinate remediation efforts.

  • Infrastructure and platform teams own this.
  • Verify Linux systems and VXLAN exposure.
  • Plan kernel updates during maintenance windows.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Linux kernel VXLAN component?

VXLAN (Virtual Extensible LAN) is a network virtualization technology that allows organizations to extend Layer 2 networks over a Layer 3 infrastructure. It is a core part of the Linux kernel, functioning as a bridge between physical network hardware and virtualized workloads. Developers and administrators use it to manage complex cloud environments, data center connectivity, and container networking, ensuring that virtual machines and containers can communicate efficiently across different physical hosts.

What is the weakness behind CVE-2026-74475?

This vulnerability is a race condition involving how the kernel accesses network hardware addresses. In the VXLAN implementation, these addresses can be updated by the system at the same time the routing process is reading them. Without proper synchronization, the system may perform a 'torn read,' capturing an incomplete or corrupted MAC address. This logic error compromises the integrity of the kernel's network routing decisions.

How does an attacker trigger this vulnerability?

An attacker must send specially crafted network traffic that interacts with the VXLAN component. The vulnerability relies on a race condition, meaning it is most likely triggered when the kernel is processing this traffic simultaneously with legitimate updates to neighbor hardware addresses. Simply having VXLAN enabled is not enough; the bug requires specific, malformed traffic to be processed during the precise timing window where an address update is occurring.

Should I be concerned if my servers are not internet-facing?

Halo Surface Signal indicates this vulnerability is very unlikely to be directly exposed to the public internet because it exists within a low-level internal operating system component. While internet-facing systems generally carry more risk, this issue specifically affects kernel-level network routing. You should prioritize internal systems that perform heavy VXLAN-based routing, as those are the environments where such race conditions are most likely to manifest.

Do I need to patch every system immediately?

Not necessarily. Your first step is to audit your infrastructure to identify which Linux systems actively utilize VXLAN configurations. Once identified, assess the business criticality of those systems. Since this requires a kernel update, coordinate with your infrastructure or platform teams to plan the deployment during your next scheduled maintenance window rather than treating it as an emergency user-space patch.

References