CVE Catalog

CVE-2025-38674

MediumCVSS 5.5
Published: Updated: Translated: NVD NIST

Summary

In the Linux kernel, a change was reverted that caused the dma_buf field in struct drm_gem_object to become NULL when user space released the final GEM handle, resulting in a NULL-pointer dereference. The fix restores the use of .import_attach->dmabuf.

Risk Assessment

The vulnerability can cause a kernel crash (oops/panic) due to a NULL dereference, leading to system unavailability or denial of service. The risk affects systems running a vulnerable kernel version with DRM drivers.

Recommendation

Update the Linux kernel to a version containing this fix. Monitor the stability of systems with active DRM drivers and prioritize the update if needed.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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