LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38672: Revert "drm/gem-dma: Use dma_buf from GEM object instance"

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

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash affected systems when DRM/GEM DMA buffer handling hits a NULL pointer after user space releases the final GEM handle. The public record does not provide CVSS, confirmed impact beyond the crash condition, or evidence of exploitation.

Executive priority

Treat as a kernel stability issue requiring normal patch management priority unless your environment has untrusted local users or shared GPU workloads, where prioritization should increase. No source provided evidence of active exploitation.

Technical view

A prior drm/gem-dma change used the drm_gem_object dma_buf field, which is not stable for the object's lifetime. When the final user-space GEM handle is released, dma_buf may become NULL, causing a NULL-pointer dereference. The resolution reverts that change and uses import_attach->dmabuf.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions or builds containing commit e8afa1557f4f963c9a511bd2c6074a941c308685 before the referenced stable fixes. The bundle identifies Linux 6.15, 6.15.9, and 6.16 metadata, but exact distribution package status must be verified.

Exploitation context

The sources describe a kernel NULL-pointer dereference triggered by GEM DMA buffer lifetime handling. They do not state remote exploitability, privilege impact, public exploit availability, or active exploitation. KEV is false in the provided bundle.

Researcher notes

The vulnerability centers on object lifetime assumptions in drm_gem_object dma_buf. Earlier framebuffer reference workarounds were partial and did not cover buffer objects without DRM framebuffers. The fix is a revert back to import_attach->dmabuf.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable revert commits.
  • Check Linux distribution advisories for packaged fixes and reboot requirements.
  • Prioritize systems exposing DRM/GPU functionality to untrusted local users or workloads.
  • If no fixed package exists, follow vendor guidance for temporary risk reduction.

Validation and detection

  • Inventory running kernel versions and distribution package revisions.
  • Check whether the referenced stable commits are present in the running kernel source or changelog.
  • Review kernel logs for NULL-pointer dereference reports involving DRM, GEM, or dma_buf paths.
  • Confirm patched systems have rebooted into the fixed kernel.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-38672 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe8afa1557f4f963c9a511bd2c6074a941c308685, e8afa1557f4f963c9a511bd2c6074a941c308685unaffected
LinuxLinux6.15, 0, 6.15.9, 6.16affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.