Answer in brief
CVE-2026-98283 records a Unknown severity vulnerability in KVM: PPC: Book3S HV: fix use-after-free in kvmhv_emulate_tlbie_all_lpid(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e3b6b4661527e821ffbe3db83952fdb1e6e47c49 <4d8f7b1f586375df8bce23a0909566ad5e852259 || >=e3b6b4661527e821ffbe3db83952fdb1e6e47c49 <e37fba1ba69385cff2d0e60b371ee19e7d1852d1 || >=e3b6b4661527e821ffbe3db83952fdb1e6e47c49 <24b634852413229bb8340d908b115c3365f3a247 || >=e3b6b4661527e821ffbe3db83952fdb1e6e47c49 <fbf69b7d0555ee83c871f58750770f74b7179ad1 || >=e3b6b4661527e821ffbe3db83952fdb1e6e47c49 <ec2d7a52b3996ae81131617b4afc0af31583c1b4 || >=e3b6b4661527e821ffbe3db83952fdb1e6e47c49 <51938dfa8a51a4f85328413fca9b6e21f9d2d088 | 4d8f7b1f586375df8bce23a0909566ad5e852259, e37fba1ba69385cff2d0e60b371ee19e7d1852d1, 24b634852413229bb8340d908b115c3365f3a247, fbf69b7d0555ee83c871f58750770f74b7179ad1, ec2d7a52b3996ae81131617b4afc0af31583c1b4, 51938dfa8a51a4f85328413fca9b6e21f9d2d088 |
| Linux/Linuxgeneric | 4.20 | Not reported |
Published upstream
Oct 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 6, 2026
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.
Quoted source text, attributed separately from HOL analysis.