Loading vulnerability…
CVE-2024-26976 is a race condition in the Linux kernel KVM asynchronous page-fault handling lifecycle. When a KVM virtual CPU is destroyed or clears its asynchronous page-fault completion queue, pending async page-fault worker callbacks were not consistently flushed. A callback could therefore continue executing after vCPU/VM teardown and after the final reference to the KVM kernel module had been released. The affected logic attempted to retain a VM reference for the worker, but that did not prevent KVM module unloading before callback completion; additionally, releasing that reference from the callback after adding queue flushing could deadlock. The fix flushes valid pending async page-fault work before vCPU/VM destruction and handles non-queued wake-all entries separately.
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.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux KVM vulnerability involving failure to flush asynchronous page-fault work when a virtual CPU is destroyed.
Linux kernel KVM asynchronous page-fault workqueue cleanup flaw.
Linux kernel KVM asynchronous page-fault workqueue cleanup flaw.
Linux kernel KVM asynchronous page-fault workqueue cleanup flaw during vCPU destruction.
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.