# CVE-2026-89928: KVM: x86/mmu: Consume the locked rmap value in the lockless rmap walk CVE-2026-89928 is fixed in 20 products on 1 platform, first by DEBIAN-CVE-2026-89928, released September 23, 2026. It is not reported as exploited. Patch Radar priority: High. - Web page: https://patchblox.com/security/cve/CVE-2026-89928 - Priority: High - CVSS: 8.8 (high) - EPSS: 0.0017 - CISA KEV: not listed - Exploited (vendor report): no - Publicly disclosed: no - Published: Sep 16, 2026 - Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-89928 ## Description In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: Consume the locked rmap value in the lockless rmap walk __kvm_rmap_lock() deliberately elides the rmap lock when it observes an empty rmap. In that case kvm_rmap_lock_readonly() also re-enables preemption and returns zero, so the caller holds neither the rmap lock nor a preemption reference. The elision documents the invariant it relies on: * Elide the lock if the rmap is empty, as lockless walkers (read-only * mode) don't need to (and can't) walk an empty rmap, nor can they add * entries to the rmap. I.e. the only paths that process empty rmaps * do so while holding mmu_lock for write, and are mutually exclusive. kvm_rmap_age_gfn_range() ignores the returned value and unconditionally enters for_each_rmap_spte_lockless(). The iterator started with rmap_get_first(), which re-reads rmap_head->val rather than using the value returned by the lock. If a writer populates the rmap between the lock's read and the iterator's re-read, the aging path walks the newly installed rmap without holding its lock. For a KVM_RMAP_MANY rmap this leaves the walker following a pte_list_desc chain that it never locked. A writer holding mmu_lock for write may free that chain (e.g. kvm_zap_all_rmap_sptes() on the recycle path, or any rmap zap) via kmem_cache_free() while the walk is in progress, giving a slab use-after-free. Nothing serialises the two: the aging path runs without mmu_lock when CONFIG_KVM_MMU_LOCKLESS_AGING=y, and the rmap lock that would otherwise exclude the writer was elided. Because the empty path re-enables preemption, the interval between the two reads can span an arbitrary scheduling delay. Fix the class of bug by having the lockless walk consume the value returned by the lock instead of re-reading the rmap. Split rmap_get_first() into __rmap_get_first(), which starts an iterator from an already-read rmap value, and make for_each_rmap_spte_lockless() take that value and call __rmap_get_first() directly. kvm_rmap_age_gfn_range() passes the value returned by kvm_rmap_lock_readonly(): when the lock was elided the value is zero, __rmap_get_first() returns NULL, and the walk is skipped. No lockless walker re-reads the rmap, so the lock-elision invariant cannot be violated, and no lock()-without-paired-unlock() path is added to the aging code. ## Where it's fixed | Platform | Product | Fixed in | Fix | Released | |---|---|---|---|---| | Linux | bpftool6.18 amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | bpftool6.18-debuginfo amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | kernel-livepatch-6.18.51-120.162 amzn 2023 | 1:1.0-0.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | kernel6.18 amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | kernel6.18-debuginfo amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | kernel6.18-debuginfo-common-aarch64 amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | kernel6.18-debuginfo-common-x86_64 amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | kernel6.18-devel amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | kernel6.18-headers amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | kernel6.18-modules-extra amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | kernel6.18-modules-extra-common amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | kernel6.18-tools amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | kernel6.18-tools-debuginfo amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | kernel6.18-tools-devel amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | linux Debian 14 | 7.2.6-1 | [DEBIAN-CVE-2026-89928](https://patchblox.com/security/data/fix/linux/debian-cve-2026-89928.md) | Sep 23, 2026 | | Linux | microvm-kernel6.18 amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | perf6.18 amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | perf6.18-debuginfo amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | python3-perf6.18 amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | | Linux | python3-perf6.18-debuginfo amzn 2023 | 1:6.18.51-120.162.amzn2023 | [ALAS2023-2026-3187](https://patchblox.com/security/data/fix/linux/alas2023-2026-3187.md) | Nov 7, 2026 | --- Data as of 2026-11-08T00:53:09Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.