CVE-2026-98283
8.8 HIGHPublished 2026-10-06 · Updated 2026-10-07
AI risk analysis
- Summary
- The flaw allows a concurrent vCPU to race with the free path of another vCPU, leading to a use-after-free condition and potential memory corruption.
- Exploitability
- Exploitation requires precise timing and concurrent access, making it moderately difficult. Precondition is the presence of nested virtualization and concurrent vCPU activity.
- Blast radius
- If exploited, it could lead to arbitrary code execution or system instability, impacting the virtualized environment and potentially the host system.
- Detection
- No reliable host or network indicator is derivable from the published description.
- Prioritized remediation
- Upgrade to the fixed version 5.19-rc1 or later.
Analysis generated locally by qwen2.5:7b-instruct (no data left the box). AI-assisted — verify against primary sources before acting.
NVD description
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.
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
All references
- https://git.kernel.org/stable/c/24b634852413229bb8340d908b115c3365f3a247
- https://git.kernel.org/stable/c/4d8f7b1f586375df8bce23a0909566ad5e852259
- https://git.kernel.org/stable/c/51938dfa8a51a4f85328413fca9b6e21f9d2d088
- https://git.kernel.org/stable/c/e37fba1ba69385cff2d0e60b371ee19e7d1852d1
- https://git.kernel.org/stable/c/ec2d7a52b3996ae81131617b4afc0af31583c1b4
- https://git.kernel.org/stable/c/fbf69b7d0555ee83c871f58750770f74b7179ad1
Source data: NVD (nvd.nist.gov), public domain. Exploit-DB.ai adds local AI analysis for defensive use only.
Related CVEs
- HIGHCVE-2026-64561PoC
- CRITICALCVE-2026-64566
- HIGHCVE-2026-64574
- HIGHCVE-2026-71226
- CRITICALCVE-2026-89775
- HIGHCVE-2026-89789
- HIGHCVE-2026-89805
- HIGHCVE-2026-89815
Related by shared AI tags and CWE weakness class. Browse the full archive.