CVE-2026-99471

published 19 Nov 2026 · updated 22 Nov 2026

KVM: PPC: Book3S HV: Add SRCU protection for virtual-mode HPT hcalls

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel c3d0261c4fae2cc36dcf9f4e247552498232caff, Kernel 0f86aba67317d65b2dc89995dd5ddefe219411a7, Kernel 4ab2c987fd15a4bd28ef46a9ac871359886e6439 and 4 more.

In the Linux kernel, the following vulnerability has been resolved: KVM: PPC: Book3S HV: Add SRCU protection for virtual-mode HPT hcalls The virtual-mode HPT hcall handlers (H_ENTER, H_REMOVE, H_BULK_REMOVE, H_CLEAR_REF, H_CLEAR_MOD) call into book3s_hv_rm_mmu.c, which accesses memslots via kvm_memslots_raw(). kvm_memslots_raw() uses rcu_dereference_raw_check() to bypass SRCU lockdep annotation checking. This is safe in real mode because the entire guest entry/exit is wrapped in srcu_read_lock/unlock inside kvmppc_run_core() and kvmhv_run_single_vcpu(). However, since commit 6165d5dd99db ("KVM: PPC: Book3S HV: add virtual mode handlers for HPT hcalls and page faults"), these same handlers are also executed in virtual mode via kvmppc_pseries_do_hcall(), which runs after SRCU has already been released on guest exit. A concurrent KVM_SET_USER_MEMORY_REGION deletion or move can therefore call synchronize_srcu_expedited() — which does not wait for this thread — and then kfree(slot) and vfree(slot->arch.rmap) while the hcall handler still holds a raw pointer to the memslot. lock_rmap() then writes to freed vmalloc memory, leading to use-after-free and memory corruption. Because kvm_memslots_raw() suppresses lockdep checks, this race is entirely silent. Fix this by factoring out the 7 HPT hcall handlers (H_REMOVE, H_ENTER, H_READ, H_CLEAR_MOD, H_CLEAR_REF, H_PROTECT, H_BULK_REMOVE) into a helper function, kvmppc_pseries_do_hpt_hcall(), and wrapping its call site in srcu_read_lock(&kvm->srcu) / srcu_read_unlock(&kvm->srcu, idx). Targeting only the HPT hcalls avoids wrapping non-HPT hcalls that sleep (such as H_CONFER, H_REGISTER_VPA, H_PAGE_INIT) or handlers that already acquire SRCU internally (such as H_RTAS).

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=6165d5dd99dbaec7a309491c3951bd81fc89978d <c3d0261c4fae2cc36dcf9f4e247552498232caff, >=6165d5dd99dbaec7a309491c3951bd81fc89978d <0f86aba67317d65b2dc89995dd5ddefe219411a7, >=6165d5dd99dbaec7a309491c3951bd81fc89978d <4ab2c987fd15a4bd28ef46a9ac871359886e6439, >=6165d5dd99dbaec7a309491c3951bd81fc89978d <61a39797bb136243c48b46e2586d8a9e2cea6a89, =5.14c3d0261c4fae2cc36dcf9f4e247552498232caff, 0f86aba67317d65b2dc89995dd5ddefe219411a7, 4ab2c987fd15a4bd28ef46a9ac871359886e6439, 61a39797bb136243c48b46e2586d8a9e2cea6a89
linux-kernel: Kernel>=6.13.0 <6.18.61, >=6.19.0 <7.3.2, >=5.14.0 <6.12.1176.18.61, 7.3.2, 6.12.117

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-99471 severity on Zeptric[![CVE-2026-99471](https://zeptric.io/badge/cve/CVE-2026-99471.svg)](https://zeptric.io/cve/CVE-2026-99471)