CVE-2025-38669: Linux kernel · Revert "drm/gem-shmem: Use dma_buf from GEM object instance
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium : upgrade to 291a77604858a8b47cf6640a12b76e97f99e00ed or 6d496e9569983a0d7a05be6661126d0702cf94f7 when convenient.
Data as of 19 Nov 2026, 02:25 UTC
Thin evidence
One scorer or none- Patch
- Available – fixed in 291a77604858a8b47cf6640a12b76e97f99e00ed, 6d496e9569983a0d7a05be6661126d0702cf94f7
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
Upgrade Linux kernel to 291a77604858a8b47cf6640a12b76e97f99e00ed or 6d496e9569983a0d7a05be6661126d0702cf94f7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available through the revert of the problematic commit, which restores the stable usage of dma_buf references. Users should update their Linux kernel to versions that include this revert. Since this is a kernel-level issue, applying the official kernel update from the vendor or distribution is the recommended remediation. No additional workarounds are necessary as the previous partial mitigations were insufficient.
Description
CVE-2025-38669 is a medium-severity vulnerability in the Linux kernel's DRM subsystem related to the handling of dma_buf pointers in GEM objects. The dma_buf field in struct drm_gem_object can become NULL when user space releases the final GEM handle, leading to a NULL-pointer dereference and potential denial of service. Previous partial workarounds did not fully address the issue, especially for buffer objects without associated DRM framebuffers. The vulnerability was resolved by reverting a commit that introduced the unstable dma_buf usage and returning to a more stable reference approach.