cve.bz

CVE-2026-98606 linux linux

no score yetEPSS 0.2%Fix available

linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: drm/virtio: release the GEM object on virtio_gpu_vram_create() errors virtio_gpu_vram_create() frees the object with a bare kfree(vram) on both error paths after drm_gem_private_object_init() has run, and on the second one after drm_gem_create_mmap_offset() has linked obj->vma_node into the device's VMA offset manager. The freed object stays in that interval tree, so a later lookup or insertion walks freed memory, and the dma_resv and gpuva lock are never destroyed. Call drm_gem_object_release() before kfree() on both paths.
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 11th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 5.15.222
  • Linux Linux: fixed in 6.1.189
  • Linux Linux: fixed in 6.6.158
  • Linux Linux: fixed in 6.12.112
  • Linux Linux: fixed in 6.18.55
  • Linux Linux: fixed in 7.2.9
  • Linux Linux: fixed in 7.3
  • Debian, Ubuntu, SUSE, openSUSE, Azure Linux, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-98606 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-98606?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-98606?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-98606 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-98606

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-98606](https://cve.bz/cve/badge/CVE-2026-98606.svg)](https://cve.bz/cve/CVE-2026-98606)

HTML:

<a href="https://cve.bz/cve/CVE-2026-98606"><img src="https://cve.bz/cve/badge/CVE-2026-98606.svg" alt="CVE-2026-98606"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux5.11 and later

Fixed in

ProductRelease lineFixed in
Linux5.155.15.222
Linux6.16.1.189
Linux6.66.6.158
Linux6.126.12.112
Linux6.186.18.55
Linux7.27.2.9
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.190-1DEBIAN-CVE-2026-98606
Debian12linux-6.126.12.113-1~deb12u1DEBIAN-CVE-2026-98606
Debian13linux6.12.113-1DEBIAN-CVE-2026-98606
Debian14linux7.2.9-1DEBIAN-CVE-2026-98606
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-98606
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-98606
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-98606
Ubuntu22.04:LTSlinux5.15.0-202.212UBUNTU-CVE-2026-98606 USN-8961-1
Ubuntu22.04:LTSlinux-aws5.15.0-1119.126UBUNTU-CVE-2026-98606 USN-8961-1
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1069.74~22.04.1UBUNTU-CVE-2026-98606 USN-9024-1
Ubuntu22.04:LTSlinux-azure5.15.0-1125.134UBUNTU-CVE-2026-98606 USN-8961-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1073.82~22.04.1UBUNTU-CVE-2026-98606 USN-9026-1
Ubuntu22.04:LTSlinux-azure-fde5.15.0-1124.133UBUNTU-CVE-2026-98606
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1071.78~22.04.1UBUNTU-CVE-2026-98606 USN-9026-1
Ubuntu22.04:LTSlinux-gcp5.15.0-1120.130UBUNTU-CVE-2026-98606 USN-8961-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1073.81~22.04.1UBUNTU-CVE-2026-98606 USN-9024-1
78 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise High Availability Extension 15 SP7, Linux Enterprise Live Patching 15 SP7, Linux Enterprise Module for Legacy 15 SP7 and 1 morekernel-default6.4.0-150700.53.90.1SUSE-SU-2026:5091-1
SUSELinux Enterprise High Availability Extension 16.0kernel-default6.12.0-160000.41.1SUSE-SU-2026:24651-1
SUSELinux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7_Update_241-150700.15.3.1SUSE-SU-2026:5091-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-64kb, kernel-source, kernel-default and 1 more6.4.0-150700.53.90.1SUSE-SU-2026:5091-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-default-base6.4.0-150700.53.90.1.150700.17.51.1SUSE-SU-2026:5091-1
SUSELinux Enterprise Module for Development Tools 15 SP7kernel-docs, kernel-syms, kernel-source and 1 more6.4.0-150700.53.90.1SUSE-SU-2026:5091-1
SUSELinux Enterprise Module for Public Cloud 15 SP7kernel-azure6.4.0-150700.53.90.1SUSE-SU-2026:5091-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-64kb, kernel-docs, kernel-syms and 6 more6.12.0-160000.41.1SUSE-SU-2026:24662-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-default-base6.12.0-160000.41.1.160000.2.32SUSE-SU-2026:24662-1
SUSELinux Enterprise Server for NVIDIA 16.1kernel-nvidia64kb, kernel-source-nvidia6.12.0-160100.7.1SUSE-SU-2026:24705-1
SUSELinux Micro 6.0kernel-default-base6.4.0-159998.55.1.159998.21.42SUSE-SU-2026:24550-1
SUSELinux Micro 6.0kernel-source, kernel-default, kernel-kvmsmall6.4.0-159998.55.1SUSE-SU-2026:24550-1
5 more for SUSE in the JSON and on SUSE's page.
openSUSELeap 16.0kernel-default-base6.12.0-160000.41.1.160000.2.31openSUSE-SU-2026:22266-1
openSUSELeap 16.0kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160000.41.1openSUSE-SU-2026:22266-1
openSUSELeap 16.1kernel-default-base6.12.0-160100.9.1.160100.3.14openSUSE-SU-2026:22309-1
openSUSELeap 16.1kernel-nvidia64kb, kernel-syms-nvidia, kernel-source-nvidia6.12.0-160100.7.1openSUSE-SU-2026:22307-1
openSUSELeap 16.1kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160100.9.1openSUSE-SU-2026:22309-1
Azure Linux3kernel6.6.159.1-1AZL-108884
Alpaquita23linux-lts6.1.189-r0BELL-CVE-2026-98606
Alpaquita25linux-lts6.12.112-r0BELL-CVE-2026-98606
Alpaquitastreamlinux-lts6.18.55-r0BELL-CVE-2026-98606

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated Moderate because exploitation requires local authenticated access inside a virtual guest configured with a VirtIO GPU adapter, alongside inducing specific resource allocation failure conditions. Physical hardware systems and virtual instances not utilizing VirtIO virtualized graphics devices are not exposed. On systems configured with the device, an authenticated local attacker with direct rendering access could cause a kernel crash or potentially elevate privileges.

Red Hat's mitigation

--- 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)

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelAffected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelAffected
Red Hat Enterprise Linux 8kernel-rtAffected
Red Hat Enterprise Linux 9kernelAffected
Red Hat Enterprise Linux 9kernel-rtAffected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-98606.

References

Check your stackJSON