CVE-2026-98607: Linux kernel · drm/virtio: fix object leaks in virtio_gpu_resource_create_blob_ioctl()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in eea473532a286cd1b13cddbec5c645989f43a3aa : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:05 UTC
Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in eea473532a286cd1b13cddbec5c645989f43a3aa, 0455867bbd95ffa9d9db0a1c6dda500f8126232c, 88c60c06a2a5244f5dd32ec098e633add114890f +4
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in the Linux kernel as indicated by the presence of fixed commits. Users should update to a Linux kernel version that includes these fixes to resolve the resource leak issue.
Description
A vulnerability in the Linux kernel's drm/virtio component caused object leaks in the virtio_gpu_resource_create_blob_ioctl() function. The issue arises because drm_gem_object_release() was incorrectly called on error paths instead of dropping the reference, preventing proper resource freeing and causing leaks of virtio_gpu_object, resource IDs, and host-side resources. This flaw has been fixed by using drm_gem_object_put() to correctly release references.
References
- git.kernel.org/stable/c/73ea38a89b923fa08047885a0845d1cd89261ead (opens in a new tab)
- git.kernel.org/stable/c/eea473532a286cd1b13cddbec5c645989f43a3aa (opens in a new tab)
- git.kernel.org/stable/c/88c60c06a2a5244f5dd32ec098e633add114890f (opens in a new tab)
- git.kernel.org/stable/c/0455867bbd95ffa9d9db0a1c6dda500f8126232c (opens in a new tab)
- git.kernel.org/stable/c/81c6769e069d703154087377d1749af2f1b74e49 (opens in a new tab)
- git.kernel.org/stable/c/02df4e24dc4c0bf5b0425a6acabc5201d7f04fc2 (opens in a new tab)
- git.kernel.org/stable/c/24b6d5c7641412c9ebef0d4c8b888d49a0e6b880 (opens in a new tab)