A newly discovered vulnerability in the Linux kernel, named Zapscape, poses a significant threat to KVM hosts by allowing attackers with kernel privileges in an L1 guest virtual machine (VM) to escape isolation and execute code on the host system. This defect, identified as CVE-2026-64561, is particularly concerning when nested virtualization is accessible to untrusted guests.
Understanding the Zapscape Flaw
The Zapscape vulnerability affects the shadow memory management unit (MMU) of KVM/x86, which is responsible for managing shadow page tables crucial for nested guest memory translation. The security flaw, disclosed by researcher Hyunwoo Kim, enables an exploit path that can execute commands on the host with root privileges.
An upstream fix has been incorporated, advising administrators managing KVM hosts with exposed nested virtualization to apply a stable kernel patch or vendor-provided package updates. Notably, L1 kernel privilege typically requires guest root access, alongside specific conditions for Intel systems involving EPT page-walk lengths.
Technical Insights into the Flaw
The Zapscape issue is identified as a stale-root check ordering flaw within KVM’s shadow-MMU bookkeeping. This flaw can result in a use-after-free scenario during guest-triggered page fault handling. In these instances, KVM might reclaim MMU pages and invalidate the shadow MMU root page, failing to recheck the root, thus leading to continued operations under an invalidated root.
Kim’s technical assessment highlights a use-after-free in the recursive zap path during shadow page reclamation. Failure to revalidate the root can cause child shadow pages to inherit an invalid state, eventually leading to dangling links and potential post-free write vulnerabilities.
Proof-of-Concept and Industry Response
Kim has developed a proof-of-concept targeting AMD nested SVM/NPT on Linux 7.1.3, advising that it be safely executed under QEMU TCG. Although QEMU itself is not vulnerable, the bug resides within KVM’s kernel, independent of QEMU’s emulation. Kim states that while the proof-of-concept is public, there is no indication of the flaw being exploited in real-world scenarios.
The National Vulnerability Database has identified Linux versions 5.9 and later as affected, recommending updates to fixed stable releases. Red Hat has preliminarily rated the flaw with a CVSS score of 7.0, categorizing it as an expired pointer dereference.
Red Hat further advises that package statuses may vary across different Linux vendors, with backported fixes potentially present without version string updates. As of the latest reports, Debian’s tracker flags certain kernel packages as vulnerable, with others marked as fixed.
The disclosure timeline reveals that Kim reported the vulnerability to the kernel security team in July 2026, with the issue being publicly disclosed in early August following the assignment of CVE-2026-64561. The fix, now part of the kernel, modifies the stale-root check order to enhance system security.
