CVE-2024-46738 is a use-after-free vulnerability in the Linux kernel VMware VMCI subsystem. The resource-removal logic in vmci_resource_remove() identified entries using only the context and resource portions of a handle, without validating the resource type. Distinct resource types can therefore share the same context and resource values. Removing one such resource may remove a different table entry while the intended object is freed, leaving a dangling pointer in the VMCI resource table. Subsequent resource-table operations can dereference the freed object.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-impact local vulnerability requiring low privileges and no user interaction, with potential for high confidentiality, integrity, and availability impact. The supplied content does not identify the affected component or product version.
A Linux kernel use-after-free vulnerability in VMCI resource removal within vmci_resource_remove().
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.