Zapscape is a guest-to-host escape vulnerability in the Linux kernel's KVM/x86 implementation, tracked as CVE-2026-64561. The flaw resides in shadow MMU emulation, specifically in the recursive shadow-page reclamation ("zap") path. When shadow pages are reclaimed, an in-use MMU root can be zapped and marked invalid, but KVM may still proceed to make MMU pages available and then map memory through that stale, invalid, or obsolete root. Although populating an invalid root may not immediately fail, child shadow pages inherit the parent's role state, causing newly created child pages to also be marked invalid while still being inserted into the active MMU page list. This violates KVM's invariant that invalid shadow pages must never appear on the active list and results in a use-after-free condition in the host hypervisor's shadow page management. The issue affects KVM/x86 on both Intel and AMD hosts and is associated with the code path introduced in Linux 5.9 that made the invariant violation security-relevant.
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.
28 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.