drm/virtio: fix object leaks in virtio_gpu_resource_create_blob_ioctl()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 897b4d1acaf56314652c6a8e75d9f86b5e45638d · < 02df4e24dc4c0bf5b0425a6acabc5201d7f04fc2| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's virtio GPU blob creation ioctl leaks a GPU object, resource ID, and host-side resource when UUID assignment or GEM handle creation fails. The input does not establish whether an attacker can trigger these failures or specify access or interaction requirements.
Engineers running Linux kernels with the virtio GPU driver should check their versions; affected versions are not specified.