CVE-2026-98283KVM: PPC: Book3S HV: fix use-after-free in kvmhv_emulate_tlbie_all_lpid()
- 8.8HighCVSS base score
- 0.13%Exploitation in 30 daysEPSS · top 98% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 11 days later
· 11 days later
Published
- 13 days later
· 13 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High8.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High8.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.13% · top 98% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.
Affected products
- affected e3b6b4661527e821ffbe3db83952fdb1e6e47c49 – < 4d8f7b1f586375df8bce23a0909566ad5e852259
- affected e3b6b4661527e821ffbe3db83952fdb1e6e47c49 – < e37fba1ba69385cff2d0e60b371ee19e7d1852d1
- affected e3b6b4661527e821ffbe3db83952fdb1e6e47c49 – < 24b634852413229bb8340d908b115c3365f3a247
- affected e3b6b4661527e821ffbe3db83952fdb1e6e47c49 – < fbf69b7d0555ee83c871f58750770f74b7179ad1
- affected e3b6b4661527e821ffbe3db83952fdb1e6e47c49 – < ec2d7a52b3996ae81131617b4afc0af31583c1b4
- affected e3b6b4661527e821ffbe3db83952fdb1e6e47c49 – < 51938dfa8a51a4f85328413fca9b6e21f9d2d088
- affected 4.20
- unaffected < 4.20
- unaffected 6.1.189 – ≤ 6.1.*
- unaffected 6.6.158 – ≤ 6.6.*
- unaffected 6.12.112 – ≤ 6.12.*
- unaffected 6.18.54 – ≤ 6.18.*
- unaffected 7.2.8 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/4d8f7b1f586375df8bce23a0909566ad5e852259 (opens in a new tab)
- https://git.kernel.org/stable/c/e37fba1ba69385cff2d0e60b371ee19e7d1852d1 (opens in a new tab)
- https://git.kernel.org/stable/c/24b634852413229bb8340d908b115c3365f3a247 (opens in a new tab)
- https://git.kernel.org/stable/c/fbf69b7d0555ee83c871f58750770f74b7179ad1 (opens in a new tab)
- https://git.kernel.org/stable/c/ec2d7a52b3996ae81131617b4afc0af31583c1b4 (opens in a new tab)
- https://git.kernel.org/stable/c/51938dfa8a51a4f85328413fca9b6e21f9d2d088 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-93211 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-98283)Record last updated .