CVE-2025-37799 is a Linux kernel vmxnet3 driver flaw in the XDP packet-processing path. For packets processed through ring0, typically 128 bytes to 3 KB, vmxnet3_process_xdp initializes packet bounds using an incorrect buffer length. This can cause transmission of bytes beyond the legitimate packet contents, appending uninitialized data from the backing kernel page. The defect arose from using rbi->len rather than the descriptor-supplied rcd->len when preparing the XDP buffer.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel vmxnet3 driver flaw involving malformed packet sizing in vmxnet3_process_xdp, affecting Rocky Linux 10.0 kernel packages covered by CIQ advisory crlsa-2025_10371.
A Linux kernel vmxnet3 driver flaw involving malformed packet sizing in vmxnet3_process_xdp, addressed by the CIQ/Rocky Linux advisory.
A Linux kernel VMware vmxnet3 driver vulnerability caused by malformed packet sizing in vmxnet3_process_xdp.
A Linux kernel vmxnet3 issue involving malformed packet sizing in vmxnet3_process_xdp.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.