CVE Catalog

CVE-2025-38672

MediumCVSS 5.5
Published: Updated: Translated: NVD NIST

Summary

In the Linux kernel, a previous change regarding the dma_buf field in struct drm_gem_object was reverted because the field is not stable over the object's lifetime. The field becomes NULL when user space releases the final GEM handle, leading to a NULL-pointer dereference.

Risk Assessment

This can cause kernel crashes (oops/panic) and denial of service on systems with DRM graphics. It requires local access but can destabilize the system.

Recommendation

Update the Linux kernel to a version containing the fix (revert). Avoid outdated kernels on systems with active DRM drivers.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

In the Linux kernel, the following vulnerability has been resolved: Revert "drm/gem-dma: Use dma_buf from GEM object instance" This reverts commit e8afa1557f4f963c9a511bd2c6074a941c308685. 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

Vulnerability data from NVD (NIST) · CISA KEV · EPSS