Heimdall Security Logo

CVE-2026-98433

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
Linux•Linux•Versions : <=6.1.*, <=6.12.*, <8f3b7746874b39fc20e0363c9076c7787d4765ba, 0, <dfb84274932737e338ff5eb27f34b4c8ecb01b50, <ed2f2ff63cb7e71204096e765c6d02c3b6974b95, <a933d7024359e2e566b07903d1294b84f90482ae, ca9f4942670c37407bb109090eaf776ce2ccc54c, 6.12.112, 5.10.271, 6.6.158, <=5.10.*, <=6.6.*, 6.1.189, <c41088b2765af1e97e7bb05f906ae1823eca0388, 7.2.8, <5.5, <=6.18.*, 5.15.222, 5.5, <=7.2.*, <=*, <=5.15.*, <fcbff8008b0e08cd53b611bd0ff7e01f5b962f80, <0a416ee20bcccddf91ca5b63696a23b9d11d73aa, 6.18.54, <f3d4b2fc30c97cf8e6f8b880d2de9c17ecac7f5b, 7.3

Description

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.

Gravité et risque d'exploitation

CVE-2026-98433 obtient un score CVSS de 0.0/10, soit une gravité non évaluée.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, <8f3b7746874b39fc20e0363c9076c7787d4765ba, 0, <dfb84274932737e338ff5eb27f34b4c8ecb01b50, <ed2f2ff63cb7e71204096e765c6d02c3b6974b95, <a933d7024359e2e566b07903d1294b84f90482ae, ca9f4942670c37407bb109090eaf776ce2ccc54c, 6.12.112, 5.10.271, 6.6.158, <=5.10.*, <=6.6.*, 6.1.189, <c41088b2765af1e97e7bb05f906ae1823eca0388, 7.2.8, <5.5, <=6.18.*, 5.15.222, 5.5, <=7.2.*, <=*, <=5.15.*, <fcbff8008b0e08cd53b611bd0ff7e01f5b962f80, <0a416ee20bcccddf91ca5b63696a23b9d11d73aa, 6.18.54, <f3d4b2fc30c97cf8e6f8b880d2de9c17ecac7f5b, 7.3) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE