CVE-2026-64561: KVM: x86: Check for invalid/obsolete root *after* making MMU pages available
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.150.1-1
Event History
Frequently Asked Questions
What is the severity of CVE-2026-64561?
CVE-2026-64561 has a risk rating of 44, indicating a moderate severity level.
How do I fix CVE-2026-64561?
To fix CVE-2026-64561, you should update to the latest version of the Linux kernel that contains the patch for this vulnerability.
What systems are affected by CVE-2026-64561?
CVE-2026-64561 affects systems utilizing the Linux kernel that incorporates the KVM x86 virtualization feature.
What are the potential impacts of CVE-2026-64561?
The potential impacts of CVE-2026-64561 include the risk of system instability or exploitation due to improper handling of MMU pages.
Is CVE-2026-64561 publicly disclosed?
Yes, CVE-2026-64561 was publicly disclosed with details on August 4, 2026.