CVE detail
CVE-2026-64561
In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Check for invalid/obsolete root *after* making MMU pages available Check for a "stale" page fault, i.e. for an invalid and/or obsolete root, after making MMU pages available for the shadow MMU. If reclaiming shadow pages zaps an in-use root, i.e. marks it invalid, then KVM will attempt to map memory into an invalid root. On its own, populating an invalid root is "fine", but because child shadow pages inherit their parent's role, any children created during the map/fetch will be created as invalid pages, thus violating KVM's invariant that invalid pages are never on the list of active MMU pages. Note, the underlying flaw has existed since KVM first started tracking invalid roots in 2008 (commit 2e53d63acba7, "KVM: MMU: ignore zapped root pagetables"), but the true badness only came along in 2020 (Linux 5.9) with the invariant that invalid shadow pages can't be on the list of active pages. Note #2, inheriting role.invalid when creating child shadow pages is also far from ideal; that flaw will be addressed separately.
Buzz score
Why this CVE is surfacing
This all-time snapshot uses the same composite formula as Trending across a 30-year evidence window, rather than a current rolling window.
Buzz score components · mention 23.0 · diversity 20.0 · KEV 0.0 · OTX 0.0 · PoC 0.0
Why it matters now
Mention timeline
- Total mentions
- 9
- within the 30d window
- Peak daily
- 6
- highest bucket
Evidence
Source links by recency
9 source links · newest first
- CVE-2026-64561 KVM: x86: Check for invalid/obsolete root *after* making MMU pages availableMicrosoft MSRC
Information published.
vendormsrc.microsoft.comAug 9, 2026, 8:41 AM te code on the host. The risk applies when nested virtualization is exposed to untrusted guests. The flaw is tracked as CVE-2026-64561 and affects KVM/x86's shadow memory management unit (MMU), which manages shadow page
newsthehackernews.comAug 6, 2026, 5:58 PMLinked URL: https://github.com/V4bel/Zapscape | Posted by john_strinlai | 65 points | 9 comments
communitynews.ycombinator.comAug 6, 2026, 4:24 PM- https://github.com/V4bel/Zapscapegithub.com
No excerpt available.
Exploitgithub.comAug 4, 2026, 7:16 AM No excerpt available.
Exploitgit.kernel.orgAug 4, 2026, 7:16 AMNo excerpt available.
Exploitgit.kernel.orgAug 4, 2026, 7:16 AMNo excerpt available.
Exploitgit.kernel.orgAug 4, 2026, 7:16 AMNo excerpt available.
Exploitgit.kernel.orgAug 4, 2026, 7:16 AMNo excerpt available.
Exploitgit.kernel.orgAug 4, 2026, 7:16 AM
Exploit code
Public exploit repository references
Public PoC repositories are third-party, potentially unsafe artifacts. Treat their code as untrusted and use it only on authorized systems in an isolated, least-privilege environment. cvebuzz does not execute the code or verify that an exploit works.