virtio_gpu_resource_create_ioctl in the Linux kernel incorrectly calls drm_gem_object_release() on error paths instead of dropping the reference it owns. This prevents drm_gem_object->funcs->free() from executing, causing the virtio_gpu_object, its memory pages, scatter‑gather table, resource ID, and the host‑side resource to persist in memory. The persistent allocation leads to a resource leak that can grow until system resources are exhausted, resulting in a denial‑of‑service condition.

The vulnerability affects the Linux kernel's virtio GPU driver across all kernel releases that implement this ioctl path. No specific kernel version is listed as fixed, so all current or older kernels that contain the unpatched code are vulnerable. The impact applies to any system running the affected kernel and using virtio GPU devices.

Because the leak occurs during an ioctl call, the attack requires an entity that can invoke the virtio_gpu_resource_create_ioctl interface, typically a user‑space process with access to the GPU device node. The exploit path is local; an attacker could repeatedly trigger the ioctl with invalid parameters to accumulate leaked objects until memory exhaustion occurs. EPSS and KEV metrics are not available, and the CVSS score is not listed, so risk assessment relies on the described mechanism. The vulnerability is not currently listed in CISA KEV, suggesting no known active exploitation, but the potential for DoS warrants timely remediation.