CVE-2026-98283

published 6 Oct 2026 · updated 20 Nov 2026

KVM: PPC: Book3S HV: fix use-after-free in kvmhv_emulate_tlbie_all_lpid()

8.8HighCVSS 8.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 fbf69b7d0555ee83c871f58750770f74b7179ad1, Kernel 24b634852413229bb8340d908b115c3365f3a247, Kernel 4d8f7b1f586375df8bce23a0909566ad5e852259 and 8 more.

In the Linux kernel, the following vulnerability has been resolved: KVM: PPC: Book3S HV: fix use-after-free in kvmhv_emulate_tlbie_all_lpid() kvmhv_emulate_tlbie_all_lpid() iterates the nested-guest IDR and drops mmu_lock before calling kvmhv_emulate_tlbie_lpid(), but does not hold a reference on the kvm_nested_guest pointer obtained from the IDR. A concurrent vCPU issuing a single-LPID tlbie (is=2, ric=2) can race through kvmhv_flush_nested() -> kvmhv_remove_nested() -> idr_remove / --refcnt -> kvmhv_release_nested() -> kfree(gp) in that window, leaving the iterating vCPU with a dangling pointer. The subsequent mutex_lock(&gp->tlb_lock) and accesses to gp->shadow_pgtable, gp->shadow_lpid and gp->l1_host all touch freed memory. The free path is fully L1-controlled. Fix this by incrementing gp->refcnt inside the loop before dropping mmu_lock, mirroring what kvmhv_get_nested() does, and releasing the reference with kvmhv_put_nested() after the per-guest work completes. This is the same get/put discipline already used at every other call site that drops mmu_lock while holding a nested-guest pointer.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=e3b6b4661527e821ffbe3db83952fdb1e6e47c49 <fbf69b7d0555ee83c871f58750770f74b7179ad1, >=e3b6b4661527e821ffbe3db83952fdb1e6e47c49 <24b634852413229bb8340d908b115c3365f3a247, >=e3b6b4661527e821ffbe3db83952fdb1e6e47c49 <4d8f7b1f586375df8bce23a0909566ad5e852259, >=e3b6b4661527e821ffbe3db83952fdb1e6e47c49 <51938dfa8a51a4f85328413fca9b6e21f9d2d088, >=e3b6b4661527e821ffbe3db83952fdb1e6e47c49 <e37fba1ba69385cff2d0e60b371ee19e7d1852d1, >=e3b6b4661527e821ffbe3db83952fdb1e6e47c49 <ec2d7a52b3996ae81131617b4afc0af31583c1b4, =4.20fbf69b7d0555ee83c871f58750770f74b7179ad1, 24b634852413229bb8340d908b115c3365f3a247, 4d8f7b1f586375df8bce23a0909566ad5e852259, 51938dfa8a51a4f85328413fca9b6e21f9d2d088, e37fba1ba69385cff2d0e60b371ee19e7d1852d1, ec2d7a52b3996ae81131617b4afc0af31583c1b4
linux-kernel: Kernel>=6.13.0 <6.18.54, >=6.19.0 <7.2.8, >=6.2.0 <6.6.158, >=6.7.0 <6.12.112, >=4.20.0 <6.1.1896.18.54, 7.2.8, 6.6.158, 6.12.112, 6.1.189

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-98283 severity on Zeptric[![CVE-2026-98283](https://zeptric.io/badge/cve/CVE-2026-98283.svg)](https://zeptric.io/cve/CVE-2026-98283)