Medium

Linux vmxnet3 XDP transmit packet corruption

IdentifiersCVE-2024-58099CWE-682

CVE-2024-58099 is an incorrect DMA-address calculation in the Linux kernel vmxnet3 driver's XDP transmit path, specifically vmxnet3_xdp_xmit_frame(). The function uses the fixed VMXNET3_XDP_HEADROOM offset when deriving the DMA address from the backing page. This assumption is invalid when a native XDP BPF program adjusts the packet data pointer, such as by prepending an IP-in-IP encapsulation header. Although the transmitted buffer length remains correct, the DMA address references the wrong packet offset, causing packet corruption.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An attacker or workload able to execute an applicable native XDP BPF program can cause vmxnet3 to transmit corrupted packets. The corrupted traffic is generally dropped in transit, producing connectivity failures and denial of service for affected traffic flows. This was observed with Cilium service load-balancing where packets were encapsulated and retransmitted through the same vmxnet3 interface.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by avoiding the vulnerable traffic pattern: do not use native XDP programs on vmxnet3 that add encapsulation headers such as IPIP and retransmit packets out the same interface. Where operationally feasible, disable or rework the affected XDP-based encapsulation/load-balancing path, or use an alternative NIC/driver path not affected by this bug until patched kernels are deployed. Vendor-supplied live patching or standard kernel update mechanisms should be used where available.

Remediation

Patch, then assume compromise.

Update to a Linux kernel release incorporating the vmxnet3 XDP DMA-offset fix. Fixed upstream versions include Linux 6.6.59 and later in the 6.6 stable series, Linux 6.11.6 and later in the 6.11 stable series, and Linux 6.12 or later. For distribution kernels, install the vendor-provided kernel update that backports the fix, then reboot unless the vendor's supported live-patching mechanism applies the relevant change.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

LinuxLinux Kerneloperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

4 SOURCESView more in app

redhat accessNews

Jan 1, 2026

RHSA-2025:9584 - Security Advisory - Red Hat Customer Portal

Linux kernel vmxnet3 driver packet-corruption issue in vmxnet3_xdp_xmit_frame.

circl vulnerability lookupNews

Apr 29, 2025

CVE-2024-58099 (GCVE-0-2024-58099)

A packet corruption vulnerability in the Linux kernel's vmxnet3 driver when using XDP BPF programs that add encapsulation headers and transmit out the same interface. The bug causes incorrect DMA address calculation, resulting in corrupted packets.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity