High [CVE-2026-98606] release the GEM object on virtio_gpu_vram_create errors
This high-severity Red Hat Linux advisory covers CVE-2026-98606; related products: Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
release the GEM object on virtio_gpu_vram_create() errors. Red Hat rates this moderate (CVSS 7).
Weakness: CWE-825.
Affected products named by the advisory: Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9; Red Hat OpenShift Container Platform 4; and 1 more.
Affected products named by the advisory: Red Hat package: kernel-rt.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 12 hours ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 12 hours ago·verify at source
Mitigation checklist
- --- CME Mitigation Guidance (2026-10-20) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to release the GEM object via drm_gem_object_release() before deallocating memory on virtio_gpu_vram_create() error paths in the VirtIO GPU driver: upgrade to the fixed Kernel/Kernel Rt/Kernel Ivos Qualcomm/Openshift/Ose Rhel Coreos builds, which call drm_gem_object_release() before kfree() on both error paths in virtio_gpu_vram_create(), closing crafted VirtIO GPU VRAM creation request triggering an allocation or ID allocation error. Until patched, this is only a concern on Linux systems with the VirtIO GPU driver enabled and local user access to VirtIO GPU device nodes — Non-Linux platforms and environments without the VirtIO GPU driver enabled are unaffected — so Restrict filesystem permissions on VirtIO GPU device nodes such as /dev/dri/card* and /dev/dri/renderD* to prevent untrusted local users from submitting GPU allocation ioctls. As a compensating measure, Enable runtime memory error detection such as KASAN to detect use-after-free access when the freed GEM object VMA node is traversed in the interval tree, Enable kernel SLAB freelist hardening and integrity validation to impede predictable heap exploitation following the bare kfree call, and Enforce SELinux in enforcing mode to block unauthorized process domains from opening VirtIO GPU device nodes. These controls limit blast radius and contain exploitation, but they do not fix the underlying error-handling use-after-free defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-301 SELinux (Enforcing Mode) (medium)
Official advisory · high-confidence parse· fetched 12 hours ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.