LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38669: Revert "drm/gem-shmem: Use dma_buf from GEM object instance"

In the Linux kernel, the following vulnerability has been resolved: Revert "drm/gem-shmem: Use dma_buf from GEM object instance" This reverts commit 1a148af06000e545e714fe3210af3d77ff903c11. 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 cause a kernel NULL-pointer dereference in DRM GEM shared-memory buffer handling. In practical terms, affected systems may crash or become unstable when the vulnerable graphics buffer path is reached. The source does not provide CVSS, CWE, exploitability, or business-impact details.

Executive priority

Treat as a kernel stability risk requiring normal patch management urgency, not an emergency based on current evidence. Escalate priority for graphics-heavy Linux fleets, shared workstations, or systems where kernel crashes would disrupt operations.

Technical view

The issue reverts commit 1a148af06000e545e714fe3210af3d77ff903c11. The drm_gem_object dma_buf field can become NULL after userspace releases the final GEM handle, so using it over the object lifetime caused a NULL-pointer dereference. The fix returns to using .import_attach->dmabuf.

Likely exposure

Exposure appears limited to Linux kernels in the affected source range, including the listed 6.15/6.16 data and systems with relevant DRM GEM shmem buffer paths. Confirm against the exact kernel build and downstream vendor advisories.

Exploitation context

The provided sources do not report active exploitation, public exploit code, or CISA KEV listing. They describe a kernel NULL-pointer dereference fixed by stable kernel commits, but do not state whether attackers can reliably trigger it or what privileges are required.

Researcher notes

The source evidence is narrow: CVE metadata, affected Linux entries, and two kernel stable commits. No CVSS, CWE, trigger preconditions, privilege requirements, or exploit status are provided. Analysis should remain tied to commit presence and downstream vendor backports.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable fix.
  • Prioritize systems using DRM graphics or shared GPU buffer workflows.
  • Check Linux distribution advisories for exact fixed package versions.
  • Avoid inventing local workarounds; follow vendor kernel guidance.
  • Plan reboot windows where kernel replacement is required.

Validation and detection

  • Inventory running kernel versions across Linux assets.
  • Check whether vendor packages include the referenced stable commits.
  • Review kernel logs for DRM GEM NULL dereference crashes.
  • Confirm no unsupported custom kernel carries the reverted commit.
  • Track CVE status for later CVSS or exploitability updates.
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-38669 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
LinuxLinux1a148af06000e545e714fe3210af3d77ff903c11, 1a148af06000e545e714fe3210af3d77ff903c11unaffected
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.