CVE-2025-38673

Source
https://cve.org/CVERecord?id=CVE-2025-38673
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38673.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2025-38673
Downstream
Published
2025-08-22T16:03:03.594Z
Modified
2026-04-02T12:48:04.656344Z
Summary
Revert "drm/gem-framebuffer: Use dma_buf from GEM object instance"
Details

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 dmabuf field in struct drmgem_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

Database specific
{
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38673.json",
    "cna_assigner": "Linux"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
cce16fcd7446dcff7480cd9d2b6417075ed81065
Fixed
e31f5a1c2cd38bf977736cdfa79444e19d4005ec
Fixed
2712ca878b688682ac2ce02aefc413fc76019cd9

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38673.json"