---
id: "CVE-2026-98607"
kind: "vulnerability"
aliases: ["CVE-2026-98607"]
title: "Linux kernel: virtio-gpu blob ioctl leaks objects on error paths"
severity: "unknown"
cvss: null
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["drm", "infrastructure", "kernel", "linux", "virtio-gpu"]
not_affected_if: []
published_at: "2026-10-18T16:17:13+00:00"
first_seen_at: "2026-10-23T21:57:16+00:00"
updated_at: "2026-10-25T05:21:27+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98607", "first_seen_at": "2026-10-23T21:57:16+00:00"}]
---

# Linux kernel: virtio-gpu blob ioctl leaks objects on error paths

In the Linux kernel's virtio-gpu DRM driver, error paths in the blob resource creation ioctl release GEM objects incorrectly, so the object, its resource id and the host-side resource are never freed. The effect described is a resource leak that can accumulate over time, and the sources do not describe code execution or data exposure.

_Summary, check and fix written by a model from the sources; labelled as such._

## Timeline

- 2026-10-23T21:57:16+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-98607

## From the sources

In the Linux kernel, the following vulnerability has been resolved:

drm/virtio: fix object leaks in virtio_gpu_resource_create_blob_ioctl()

virtio_gpu_resource_create_blob_ioctl() calls drm_gem_object_release() on
both the virtio_gpu_resource_assign_uuid() and drm_gem_handle_create()
error paths instead of dropping the reference it owns, so
obj->funcs->free() never runs and the virtio_gpu_object, the resource id
and the host-side resource are leaked.

Use drm_gem_object_put() instead.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_