A double-free vulnerability exists in the vmwgfx driver of the Linux kernel, specifically in the handling of vmw_buffer_object objects. The vulnerability arises from the lack of validation before freeing an object, allowing the same object to be freed multiple times. This can be exploited by a local privileged user to manipulate kernel memory.
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.
15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel vmwgfx double-free vulnerability involving vmw_buffer_object objects.
Linux kernel VMware graphics driver double-free vulnerability.
Linux kernel vmwgfx double-free vulnerability when handling vmw_buffer_object objects.
Linux kernel vmwgfx graphics-driver double-free vulnerability.
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.