CVE-2025-38672: Linux kernel · Revert "drm/gem-dma: Use dma_buf from GEM object instance
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 19 Nov 2026, 02:25 UTC
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 22 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
AI-suggested
The issue has been addressed by reverting the problematic commit and restoring the previous dma_buf handling method. Users should update to the Linux kernel version that includes this revert to mitigate the vulnerability. No additional workarounds are necessary as the revert fully resolves the issue.
Description
CVE-2025-38672 is a medium-severity vulnerability in the Linux kernel's DRM subsystem related to the handling of dma_buf in GEM object instances. The dma_buf field in struct drm_gem_object can become NULL when the user space releases the final GEM handle, leading to a NULL-pointer dereference. Partial workarounds were insufficient, prompting a revert to a previous implementation that uses .import_attach->dmabuf to avoid this issue.