Linux
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 versions and mitigation
From the CVE record and the vendor's references.Affected
- >= f95eec9bed76d42194c23153cb1cc8f186bf91cb, < 62ef67af1878fa2cd066642f2f59e33ade95f637
- >= f95eec9bed76d42194c23153cb1cc8f186bf91cb, < 65c4f7a1028cf01a93a2762d679c289810ede990
- >= f95eec9bed76d42194c23153cb1cc8f186bf91cb, < 35e77467610c4a37cb0ff54ee56b85f73b1f5700
- >= f95eec9bed76d42194c23153cb1cc8f186bf91cb, < 0026dbb7de8ea76e97d6edf42fc3cc084564e2bf
- >= f95eec9bed76d42194c23153cb1cc8f186bf91cb, < f3477a6a4164f15287444eda685b5f6405dbd1e5
- >= f95eec9bed76d42194c23153cb1cc8f186bf91cb, < bce0d3c26e2c761a4bf43c8949f333fc7374eb2d
- >= f95eec9bed76d42194c23153cb1cc8f186bf91cb, < 2abd5287f08319fa35764566b15c6e22cb1068db
Fixed in 62ef67af1878fa2cd066642f2f59e33ade95f637, 65c4f7a1028cf01a93a2762d679c289810ede990, 35e77467610c4a37cb0ff54ee56b85f73b1f5700, 0026dbb7de8ea76e97d6edf42fc3cc084564e2bf, f3477a6a4164f15287444eda685b5f6405dbd1e5, bce0d3c26e2c761a4bf43c8949f333fc7374eb2d, 2abd5287f08319fa35764566b15c6e22cb1068db
- 5.9
Fixed in 0, 5.15.218, 6.1.183, 6.6.148, 6.12.101, 6.18.42, 7.1.6, 7.2
Mitigation
Upgrade Linux to 62ef67af1878fa2cd066642f2f59e33ade95f637 or 65c4f7a1028cf01a93a2762d679c289810ede990 or 35e77467610c4a37cb0ff54ee56b85f73b1f5700 or 0026dbb7de8ea76e97d6edf42fc3cc084564e2bf or f3477a6a4164f15287444eda685b5f6405dbd1e5 or bce0d3c26e2c761a4bf43c8949f333fc7374eb2d or 2abd5287f08319fa35764566b15c6e22cb1068db or later.
Upgrade Linux to 0 or 5.15.218 or 6.1.183 or 6.6.148 or 6.12.101 or 6.18.42 or 7.1.6 or 7.2 or later.
Timeline
Days relative to CVE publicationFirst public PoC 2.4 days after publication; not in CISA KEV. First PoC: V4bel/Zapscape (created 6 Aug 2026, found by us: backfilled).
PoC repositories
Found on GitHub.3 PoCs · 3 informational · 1 suspicious or fake
PoCs 3
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| V4bel/Zapscape | 6 Aug 2026 +2.4 d | 177 | PoC via PoC Index |
| aarif450/Zapscape | 7 Aug 2026 +3.4 d | 2 | PoC via PoC Index |
| HackSpeak/CVE-2026-64561 | 8 Aug 2026 +3.8 d | 2 | PoC
Flags · score 30
Below the suspicion threshold (50); does not change the assessment. |
Informational 3
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| suominen/zapscape | 7 Aug 2026 +3.1 d | 0 | Informational · list |
| Aoripus-LTD/Zapscape-Fix | 7 Aug 2026 +3.2 d | 1 | Informational · detection |
| chuzhongyun/CVE-2026-64561-Kernel-Fix | 8 Aug 2026 +4.4 d | 0 | Informational · detection |
Suspicious or fake 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| HORKimhab/CVE-2026-64561 | 7 Aug 2026 +2.8 d | 3 | Fake |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.