CVE-2026-98433 — KVM: PPC: Book3S HV: fix secure device page leak on uv_page_in() failure
In the Linux kernel, the following vulnerability has been resolved: KVM: PPC: Book3S HV: fix secure device page leak on uv_page_in() failure In kvmppc_svm_page_in(), if uv_page_in() fails after kvmppc_uvmem_get_page() has succeeded, the secure device page is never released. kvmppc_uvmem_get_page() sets a bit in kvmppc_uvmem_bitmap, allocates a kvmppc_uvmem_page_pvt struct, marks the GFN as KVMPPC_GFN_UVMEM_PFN, and calls zone_device_page_init() which sets refcount=1 and locks the page. The subsequent goto out_finalize skips the *mig.dst assignment, so migrate_vma_finalize() is a no-op for the page, and none of those resources are ever reclaimed. Each occurrence permanently consumes one entry from the firmware-bounded secure memory pool (kvmppc_uvmem_bitmap), leaks pvt, and leaves the GFN marked as secure — making it unusable for the lifetime of the VM. The twin __kvmppc_svm_page_out() already handles the analogous uv_page_out() failure correctly with unlock_page(dpage); __free_page(dpage). Apply the same pattern here: unlock_page() followed by put_page(), which chains through free_zone_device_folio() into kvmppc_uvmem_folio_free() to clear the bitmap bit, free pvt, and reset the GFN state. Reachable whenever uv_page_in() returns an error (e.g. UV pool exhaustion) on any POWER9/10 + Ultravisor/PEF system.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- No scoring signals.
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ ca9f4942670c37407bb109090eaf776ce2ccc54c and < ed2f2ff63cb7e71204096e765c6d02c3b6974b95≥ ca9f4942670c37407bb109090eaf776ce2ccc54c and < 8f3b7746874b39fc20e0363c9076c7787d4765ba≥ ca9f4942670c37407bb109090eaf776ce2ccc54c and < a933d7024359e2e566b07903d1294b84f90482ae≥ ca9f4942670c37407bb109090eaf776ce2ccc54c and < c41088b2765af1e97e7bb05f906ae1823eca0388≥ ca9f4942670c37407bb109090eaf776ce2ccc54c and < f3d4b2fc30c97cf8e6f8b880d2de9c17ecac7f5b≥ ca9f4942670c37407bb109090eaf776ce2ccc54c and < dfb84274932737e338ff5eb27f34b4c8ecb01b50≥ ca9f4942670c37407bb109090eaf776ce2ccc54c and < fcbff8008b0e08cd53b611bd0ff7e01f5b962f80≥ ca9f4942670c37407bb109090eaf776ce2ccc54c and < 0a416ee20bcccddf91ca5b63696a23b9d11d73aa and 1 moreversion 5.5 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 18, 2026 – Oct 18, 2026
- 1× Official description updated · Oct 18, 2026 – Oct 18, 2026
References
8 on the record
- git.kernel.org/stable/c/0a416ee20bcccddf91ca5b63696a23b9d11d73aa
- git.kernel.org/stable/c/ed2f2ff63cb7e71204096e765c6d02c3b6974b95
- git.kernel.org/stable/c/c41088b2765af1e97e7bb05f906ae1823eca0388
- git.kernel.org/stable/c/8f3b7746874b39fc20e0363c9076c7787d4765ba
- git.kernel.org/stable/c/fcbff8008b0e08cd53b611bd0ff7e01f5b962f80
- git.kernel.org/stable/c/f3d4b2fc30c97cf8e6f8b880d2de9c17ecac7f5b
- git.kernel.org/stable/c/a933d7024359e2e566b07903d1294b84f90482ae
- git.kernel.org/stable/c/dfb84274932737e338ff5eb27f34b4c8ecb01b50
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 14h
- Unknown CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 14h
- Unknown CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 14h
- Unknown CVE-2026-98856 kprobes: Skip disarmed probes when checking optkprobe overlap 14h
- Unknown CVE-2026-98857 ipvs: bound LBLCR and LBLC cache growth 14h
- Unknown CVE-2026-98858 io_uring: fix task_work add use-after-free with SQPOLL 14h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No FIRST EPSS score.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-98433 is "KVM: PPC: Book3S HV: fix secure device page leak on uv_page_in() failure", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.