{"id":"CVE-2026-99334","summary":"KVM: PPC: Book3S HV: Add preempt_disable() around virtual-mode HPTE bit-lock users","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: PPC: Book3S HV: Add preempt_disable() around virtual-mode HPTE bit-lock users\n\nkvmppc_hv_find_lock_hpte() requires virtual-mode callers to run with\npreemption disabled, because it can return with HPTE_V_HVLOCK still held\nuntil the caller later unlocks the HPTE.  Existing virtual-mode callers\nin book3s_64_mmu_hv.c already follow that rule.\n\nTwo virtual-mode call paths do not:\n\n1. kvmppc_handle_exit_hv() calls kvmppc_hpte_hv_fault() for hash-mode\n   data-side and instruction-side faults after guest exit, with\n   preemption already enabled.  kvmppc_hpte_hv_fault() calls\n   kvmppc_hv_find_lock_hpte() directly.\n\n2. kvmppc_pseries_do_hcall() executes virtual-mode handlers for HPT\n   hcalls via kvmppc_pseries_do_hpt_hcall() with preemption enabled.\n   The handlers for H_ENTER, H_REMOVE, H_READ, H_CLEAR_MOD, H_CLEAR_REF,\n   H_PROTECT, and H_BULK_REMOVE spin on try_lock_hpte() or lock_rmap(),\n   and H_ENTER also reaches kvmppc_do_h_enter(), which uses\n   arch_spin_lock() on kvm-\u003emmu_lock.  That raw lock choice is\n   intentional because kvmppc_do_h_enter() is also used by real-mode\n   callers, so the correct fix is to establish the proper preemption\n   context at the virtual-mode caller boundary.\n\nIf a vCPU thread is preempted while holding HPTE_V_HVLOCK, any other\nthread on the same CPU trying to acquire the same bit-lock can spin\nindefinitely.  The same applies to lock_rmap() users and to the H_ENTER\npath while holding the raw mmu_lock.\n\nFix this by adding preempt_disable()/preempt_enable() pairs around the\ntwo kvmppc_hpte_hv_fault() call sites in kvmppc_handle_exit_hv(), and\naround the kvmppc_pseries_do_hpt_hcall() invocation in\nkvmppc_pseries_do_hcall().  Targeting only the HPT hcall helper avoids\nwrapping non-HPT hcalls (such as H_RTAS, H_CONFER, H_REGISTER_VPA) that\nperform page faults, blocking memory allocations, or context switches.","modified":"2026-11-19T17:00:53.533587439Z","published":"2026-11-19T14:21:40.515Z","database_specific":{"cna_assigner":"Linux","osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99334.json"},"references":[{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"},{"type":"WEB","url":"https://git.kernel.org/stable/c/7a02dfbd2f4a7dec468221d639f740a51d4483e1"},{"type":"WEB","url":"https://git.kernel.org/stable/c/8f021a671b511a49468e87a4935b43b0a4d045c0"},{"type":"WEB","url":"https://git.kernel.org/stable/c/9ffe72ff3f1ef66dc554ecafbe0861c8c118eb41"},{"type":"WEB","url":"https://git.kernel.org/stable/c/abbbe5ff83e7c9ed3a4d61b73011f1df7bf87907"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99334.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99334"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"6165d5dd99dbaec7a309491c3951bd81fc89978d"},{"fixed":"8f021a671b511a49468e87a4935b43b0a4d045c0"},{"fixed":"7a02dfbd2f4a7dec468221d639f740a51d4483e1"},{"fixed":"9ffe72ff3f1ef66dc554ecafbe0861c8c118eb41"},{"fixed":"abbbe5ff83e7c9ed3a4d61b73011f1df7bf87907"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99334.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/cve-osv-conversion/osv-output/CVE-2026-99334.json"}}],"schema_version":"1.9.2"}