{"id":"CVE-2026-99471","summary":"KVM: PPC: Book3S HV: Add SRCU protection for virtual-mode HPT hcalls","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: PPC: Book3S HV: Add SRCU protection for virtual-mode HPT hcalls\n\nThe virtual-mode HPT hcall handlers (H_ENTER, H_REMOVE, H_BULK_REMOVE,\nH_CLEAR_REF, H_CLEAR_MOD) call into book3s_hv_rm_mmu.c, which accesses\nmemslots via kvm_memslots_raw().  kvm_memslots_raw() uses\nrcu_dereference_raw_check() to bypass SRCU lockdep annotation checking.\nThis is safe in real mode because the entire guest entry/exit is wrapped\nin srcu_read_lock/unlock inside kvmppc_run_core() and\nkvmhv_run_single_vcpu().\n\nHowever, since commit 6165d5dd99db (\"KVM: PPC: Book3S HV: add virtual\nmode handlers for HPT hcalls and page faults\"), these same handlers are\nalso executed in virtual mode via kvmppc_pseries_do_hcall(), which runs\nafter SRCU has already been released on guest exit.\n\nA concurrent KVM_SET_USER_MEMORY_REGION deletion or move can therefore\ncall synchronize_srcu_expedited() — which does not wait for this thread —\nand then kfree(slot) and vfree(slot-\u003earch.rmap) while the hcall handler\nstill holds a raw pointer to the memslot.  lock_rmap() then writes to\nfreed vmalloc memory, leading to use-after-free and memory corruption.\nBecause kvm_memslots_raw() suppresses lockdep checks, this race is\nentirely silent.\n\nFix this by factoring out the 7 HPT hcall handlers (H_REMOVE, H_ENTER,\nH_READ, H_CLEAR_MOD, H_CLEAR_REF, H_PROTECT, H_BULK_REMOVE) into a\nhelper function, kvmppc_pseries_do_hpt_hcall(), and wrapping its call\nsite in srcu_read_lock(&kvm-\u003esrcu) / srcu_read_unlock(&kvm-\u003esrcu, idx).\nTargeting only the HPT hcalls avoids wrapping non-HPT hcalls that sleep\n(such as H_CONFER, H_REGISTER_VPA, H_PAGE_INIT) or handlers that already\nacquire SRCU internally (such as H_RTAS).","modified":"2026-11-20T21:02:24.898758290Z","published":"2026-11-19T14:42:57.597Z","database_specific":{"osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99471.json","cna_assigner":"Linux"},"references":[{"type":"WEB","url":"https://git.kernel.org/stable/c/0f86aba67317d65b2dc89995dd5ddefe219411a7"},{"type":"WEB","url":"https://git.kernel.org/stable/c/4ab2c987fd15a4bd28ef46a9ac871359886e6439"},{"type":"WEB","url":"https://git.kernel.org/stable/c/61a39797bb136243c48b46e2586d8a9e2cea6a89"},{"type":"WEB","url":"https://git.kernel.org/stable/c/c3d0261c4fae2cc36dcf9f4e247552498232caff"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99471.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99471"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"6165d5dd99dbaec7a309491c3951bd81fc89978d"},{"fixed":"0f86aba67317d65b2dc89995dd5ddefe219411a7"},{"fixed":"4ab2c987fd15a4bd28ef46a9ac871359886e6439"},{"fixed":"c3d0261c4fae2cc36dcf9f4e247552498232caff"},{"fixed":"61a39797bb136243c48b46e2586d8a9e2cea6a89"}]}],"database_specific":{"source":"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-99471.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.14.0"},{"fixed":"6.12.117"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.61"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"7.3.2"}]}],"database_specific":{"source":"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-99471.json"}}],"schema_version":"1.9.2"}