Revert "drm/gem-framebuffer: 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 e31f5a1c2cd38bf977736cdfa79444e19d4005ec, Kernel 6.15.9 and Kernel 2712ca878b688682ac2ce02aefc413fc76019cd9.
In the Linux kernel, the following vulnerability has been resolved: Revert "drm/gem-framebuffer: Use dma_buf from GEM object instance" This reverts commit cce16fcd7446dcff7480cd9d2b6417075ed81065. 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 | >=cce16fcd7446dcff7480cd9d2b6417075ed81065 <e31f5a1c2cd38bf977736cdfa79444e19d4005ec, =6.16, >=6.15 <6.15.9, =6.15, >=cce16fcd7446dcff7480cd9d2b6417075ed81065 <2712ca878b688682ac2ce02aefc413fc76019cd9 | e31f5a1c2cd38bf977736cdfa79444e19d4005ec, 6.15.9, 2712ca878b688682ac2ce02aefc413fc76019cd9 |
| 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