Resource leaks via incorrect blob-creation error cleanup
Published Oct 18, 2026 · Updated Oct 18, 2026
Resource leaks in Linux virtio GPU blob creation allow local users to leave guest and host GPU resources allocated after errors. The virtio_gpu_resource_create_blob_ioctl() handler calls drm_gem_object_release() without dropping its owned reference when UUID assignment or GEM handle creation fails, preventing the free callback from reclaiming the object, resource ID, and host resource. Triggering the leak requires access to the virtio GPU device and one of those failures; the published patch does not demonstrate a hang or crash.
Summary
What happened
Resource leaks in Linux virtio GPU blob creation allow local users to leave guest and host GPU resources allocated after errors. The virtio_gpu_resource_create_blob_ioctl() handler calls drm_gem_object_release() without dropping its owned reference when UUID assignment or GEM handle creation fails, preventing the free callback from reclaiming the object, resource ID, and host resource. Triggering the leak requires access to the virtio GPU device and one of those failures; the published patch does not demonstrate a hang or crash.
The record
- CVE
- CVE-2026-98607
- Published
- Oct 18, 2026
- Updated
- Oct 18, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 18, 2026CVE publishedPublication date reported by the CVE source.
- Oct 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.11
- Affected versionversion=897b4d1acaf56314652c6a8e75d9f86b5e45638d <02df4e24dc4c0bf5b0425a6acabc5201d7f04fc2
- Affected versionversion=897b4d1acaf56314652c6a8e75d9f86b5e45638d <0455867bbd95ffa9d9db0a1c6dda500f8126232c
- Affected versionversion=897b4d1acaf56314652c6a8e75d9f86b5e45638d <24b6d5c7641412c9ebef0d4c8b888d49a0e6b880
- Affected versionversion=897b4d1acaf56314652c6a8e75d9f86b5e45638d <73ea38a89b923fa08047885a0845d1cd89261ead
- Affected versionversion=897b4d1acaf56314652c6a8e75d9f86b5e45638d <81c6769e069d703154087377d1749af2f1b74e49
- Affected versionversion=897b4d1acaf56314652c6a8e75d9f86b5e45638d <88c60c06a2a5244f5dd32ec098e633add114890f
- Affected versionversion=897b4d1acaf56314652c6a8e75d9f86b5e45638d <eea473532a286cd1b13cddbec5c645989f43a3aa
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started