CVE-2026-98433KVM: PPC: Book3S HV: fix secure device page leak on uv_page_in() failure
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 18, 2026
- First seen by InfoSec Signals
- Oct 18, 2026
Affected products
Linux Linux linux:linux (from the name) | from ca9f4942670c37407bb109090eaf776ce2ccc54c before ed2f2ff63cb7e71204096e765c6d02c3b6974b95; from ca9f4942670c37407bb109090eaf776ce2ccc54c before 8f3b7746874b39fc20e0363c9076c7787d4765ba; from ca9f4942670c37407bb109090eaf776ce2ccc54c before a933d7024359e2e566b07903d1294b84f90482ae; from ca9f4942670c37407bb109090eaf776ce2ccc54c before c41088b2765af1e97e7bb05f906ae1823eca0388; from ca9f4942670c37407bb109090eaf776ce2ccc54c before f3d4b2fc30c97cf8e6f8b880d2de9c17ecac7f5b; from ca9f4942670c37407bb109090eaf776ce2ccc54c before dfb84274932737e338ff5eb27f34b4c8ecb01b50; from ca9f4942670c37407bb109090eaf776ce2ccc54c before fcbff8008b0e08cd53b611bd0ff7e01f5b962f80; from ca9f4942670c37407bb109090eaf776ce2ccc54c before 0a416ee20bcccddf91ca5b63696a23b9d11d73aa | CNA record |
References
- https://git.kernel.org/stable/c/ed2f2ff63cb7e71204096e765c6d02c3b6974b95
- https://git.kernel.org/stable/c/8f3b7746874b39fc20e0363c9076c7787d4765ba
- https://git.kernel.org/stable/c/a933d7024359e2e566b07903d1294b84f90482ae
- https://git.kernel.org/stable/c/c41088b2765af1e97e7bb05f906ae1823eca0388
- https://git.kernel.org/stable/c/f3d4b2fc30c97cf8e6f8b880d2de9c17ecac7f5b
- https://git.kernel.org/stable/c/dfb84274932737e338ff5eb27f34b4c8ecb01b50
- https://git.kernel.org/stable/c/fcbff8008b0e08cd53b611bd0ff7e01f5b962f80
- https://git.kernel.org/stable/c/0a416ee20bcccddf91ca5b63696a23b9d11d73aa
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.