Database/Kernel, userspace & hypervisor

KVM x86/mmu: lockless aging walk re-reads the rmap and can follow a pte_list_desc chain being freed
Impact
__kvm_rmap_lock() deliberately skips taking the rmap lock when the rmap is empty, on the invariant that no lockless walker will then walk it. kvm_rmap_age_gfn_range() ignored that return value and entered the iterator anyway, which re-read rmap_head->val; if a writer populated the rmap in between, the aging path walked a KVM_RMAP_MANY chain it never locked, while a writer holding mmu_lock for write can free that chain via kmem_cache_free(). The result is a slab use-after-free in the host kernel, reachable on hosts built with CONFIG_KVM_MMU_LOCKLESS_AGING=y, and the empty path re-enables preemption so the window can span an arbitrary scheduling delay. On a virtualized GPU host - vGPU or passthrough VMs from multiple tenants - host-side memory corruption is a cross-tenant problem, and patching it means rebooting a hypervisor whose VMs have to be moved first. The fix makes the lockless walk consume the value returned by the lock instead of re-reading it.
Who can reach it
Local on an x86 KVM host. Triggered by memory pressure and guest memory activity racing the MMU notifier aging path; a guest can influence both sides. Requires no host credentials beyond running a VM on the host.
What to do
Take the linked stable commits or a patched distribution kernel, then drain guests and reboot each hypervisor. Hosts built without CONFIG_KVM_MMU_LOCKLESS_AGING are not exposed to the lockless aging path, which is worth checking before scheduling a fleet-wide window.
References
Related entries
- KVM nVMX: emulated INVVPID can run on the wrong physical CPU, leaving stale L2 TLB entriesCVE-2026-89929 · Linux kernel KVM nVMX (INVVPID emulation, wrong physical CPU)High
- KVM nVMX: vpid02 is not flushed on first use after VMXOFF/VMXON, reusing another VM's TLB entriesCVE-2026-89932 · Linux kernel KVM nVMX (vpid02 allocation, last_vpid reset)High
- Linux kernel dma-direct: dma_direct_alloc_pages() treats a CPU address as a struct page pointerCVE-2026-89995 · Linux kernel dma-direct (dma_direct_alloc_from_pool return type)High
- Linux kernel mlx5_core representor TC path + net/sched tc extension: The TC_SKB_EXT skb extension is not zeroedCVE-2021-47136 · Linux kernel mlx5_core representor TC path + net/sched tc extensionHigh
- Linux kernel (net/tls): When a BPF socket policy shrinks the plaintext after the ciphertext length was computed, kTLSCVE-2025-38608 · Linux kernel (net/tls)High
- Linux kernel libceph: truncated monitor reply decodes stale bytes from the reused bufferCVE-2026-68433 · Linux kernel libceph (MON_GET_VERSION_REPLY decode bound)High
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.