Loading vulnerability…
CVE-2025-38403 is an improper initialization vulnerability in the Linux kernel's vsock/vmci transport. The vmci_transport_packet_init function did not fully initialize a vmci_transport_packet before populating its fields, leaving uninitialized data in the packet structure. The fix clears the complete structure with memset before setting packet fields.
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.
15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel vulnerability in vsock/vmci involving improper clearing of the vmci transport packet during initialization.
A Linux kernel vulnerability in the vsock/vmci component where vmci_transport_packet was not fully cleared during initialization, potentially leaving uninitialized data in the structure.
A Linux kernel vulnerability in vsock/vmci involving improper clearing of the vmci transport packet during initialization.
A Linux kernel vulnerability in vsock/vmci related to improper initialization of the vmci transport packet.
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.