Strix
72.6K

CVE-2026-98609

Unknown

Last modified

CVE-2026-98609 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: drm/virtio: fix object leak when drm_gem_handle_create() fails virtio_gpu_gem_create() owns the reference taken by virtio_gpu_object_create(). On the drm_gem_handle_create() error path it calls drm_gem_object_release() instead of dropping that reference. drm_gem_object_release() is the inverse of drm_gem_object_init() and does not touch the reference count or call obj->funcs->free(), so it is only correct as the last step of a destructor, as in virtio_gpu_cleanup_object().

Description

In the Linux kernel, the following vulnerability has been resolved: drm/virtio: fix object leak when drm_gem_handle_create() fails virtio_gpu_gem_create() owns the reference taken by virtio_gpu_object_create(). On the drm_gem_handle_create() error path it calls drm_gem_object_release() instead of dropping that reference. drm_gem_object_release() is the inverse of drm_gem_object_init() and does not touch the reference count or call obj->funcs->free(), so it is only correct as the last step of a destructor, as in virtio_gpu_cleanup_object(). Using it here leaves the bo at refcount 1 with no remaining reference, so virtio_gpu_free_object() never runs and the shmem pages, sg table and virtio_gpu_object are leaked. Since virtio_gpu_object_create() has already set bo->created, VIRTIO_GPU_CMD_RESOURCE_UNREF is not queued either, leaking the host-side resource and the resource id. drm_gem_handle_create_tail() drops the handle reference on all of its internal error paths, so the caller only has to drop its own. Use drm_gem_object_put(), matching the success path below.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= dc5698e80cf724770283e10414054662bdf6ccfa, < 13423a058187c2039aa8cb235c916be4477221b7; >= dc5698e80cf724770283e10414054662bdf6ccfa, < 687be2f8b5e0e0ca9a7028f8f6413d0ed3fbb9dc; >= dc5698e80cf724770283e10414054662bdf6ccfa, < 264ae8ac8fd625b6c118baf16c111adeee2ec632; >= dc5698e80cf724770283e10414054662bdf6ccfa, < e2edd2d78d2cf8446de017adec9598feefed3297; >= dc5698e80cf724770283e10414054662bdf6ccfa, < 372e9c3d45f664a2c000427ccbf6cdc2f99b3170; >= dc5698e80cf724770283e10414054662bdf6ccfa, < a93dce15dfef200c346b050a2acbed516cc62706; >= dc5698e80cf724770283e10414054662bdf6ccfa, < f75066c79d1eec453c0d386ef8636873d1e11f2c; >= dc5698e80cf724770283e10414054662bdf6ccfa, < 36570ef2244cc4d7563b1f0157bc0f032498638c
LinuxLinux4.2

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-98609?
In the Linux kernel, the following vulnerability has been resolved: drm/virtio: fix object leak when drm_gem_handle_create() fails virtio_gpu_gem_create() owns the reference taken by virtio_gpu_object_create(). On the drm_gem_handle_create() error path it calls drm_gem_object_release() instead of dropping that reference. drm_gem_object_release() is the inverse of drm_gem_object_init() and does not touch the reference count or call obj->funcs->free(), so it is only correct as the last step of a destructor, as in virtio_gpu_cleanup_object(). Using it here leaves the bo at refcount 1 with no remaining reference, so virtio_gpu_free_object() never runs and the shmem pages, sg table and virtio_gpu_object are leaked. Since virtio_gpu_object_create() has already set bo->created, VIRTIO_GPU_CMD_RESOURCE_UNREF is not queued either, leaking the host-side resource and the resource id. drm_gem_handle_create_tail() drops the handle reference on all of its internal error paths, so the caller only has to drop its own. Use drm_gem_object_put(), matching the success path below.
How severe is CVE-2026-98609?
Severity scoring for CVE-2026-98609 is pending analysis.
How do I fix CVE-2026-98609?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-98609?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST