drm/virtio: fix object leak when drm_gem_handle_create() fails
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux 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 Linux
4.2
- KernelLinux
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
References 8
git.kernel.org
- stable/c/13423a058187c2039aa8cb235c916be4477221b7
- stable/c/687be2f8b5e0e0ca9a7028f8f6413d0ed3fbb9dc
- stable/c/264ae8ac8fd625b6c118baf16c111adeee2ec632
- stable/c/e2edd2d78d2cf8446de017adec9598feefed3297
- stable/c/372e9c3d45f664a2c000427ccbf6cdc2f99b3170
- stable/c/a93dce15dfef200c346b050a2acbed516cc62706
- stable/c/f75066c79d1eec453c0d386ef8636873d1e11f2c
- stable/c/36570ef2244cc4d7563b1f0157bc0f032498638c