Revert "drm/gem-shmem: Use dma_buf from GEM object instance"
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 6d496e9569983a0d7a05be6661126d0702cf94f7, Kernel 6.15.9 and Kernel 291a77604858a8b47cf6640a12b76e97f99e00ed.
In the Linux kernel, the following vulnerability has been resolved: Revert "drm/gem-shmem: Use dma_buf from GEM object instance" This reverts commit 1a148af06000e545e714fe3210af3d77ff903c11. The dma_buf field in struct drm_gem_object is not stable over the object instance's lifetime. The field becomes NULL when user space releases the final GEM handle on the buffer object. This resulted in a NULL-pointer deref. Workarounds in commit 5307dce878d4 ("drm/gem: Acquire references on GEM handles for framebuffers") and commit f6bfc9afc751 ("drm/framebuffer: Acquire internal references on GEM handles") only solved the problem partially. They especially don't work for buffer objects without a DRM framebuffer associated. Hence, this revert to going back to using .import_attach->dmabuf. v3: - cc stable
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=1a148af06000e545e714fe3210af3d77ff903c11 <6d496e9569983a0d7a05be6661126d0702cf94f7, =6.16, >=6.15 <6.15.9, =6.15, >=1a148af06000e545e714fe3210af3d77ff903c11 <291a77604858a8b47cf6640a12b76e97f99e00ed | 6d496e9569983a0d7a05be6661126d0702cf94f7, 6.15.9, 291a77604858a8b47cf6640a12b76e97f99e00ed |
| linux-kernel: Kernel | >=6.15.0 <6.15.9 | 6.15.9 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket