VulnerabilityPublished 22 Aug 2025Updated 5 Nov 2026

CVE-2025-38674: Linux kernel · Revert "drm/prime: Use dma_buf from GEM object instance

Affects Linux kernelSource CVE Database V5

Not known to be exploited : upgrade to fb4ef4a52b79a22ad382bfe77332642d02aef773 or 5f05d83ce689a8930a70dfa73f879604aef8cc03 when convenient.

Data as of 5 Nov 2026, 21:34 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch

Available – fixed in fb4ef4a52b79a22ad382bfe77332642d02aef773, 5f05d83ce689a8930a70dfa73f879604aef8cc03

Exploitation 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 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to fb4ef4a52b79a22ad382bfe77332642d02aef773 or 5f05d83ce689a8930a70dfa73f879604aef8cc03.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ f83a9b8c7fd0557b0c50784bfdc1bbe9140c9bf8, < fb4ef4a52b79a22ad382bfe77332642d02aef773	Fixed in fb4ef4a52b79a22ad382bfe77332642d02aef773
LinuxLinux	Affected ≥ f83a9b8c7fd0557b0c50784bfdc1bbe9140c9bf8, < 5f05d83ce689a8930a70dfa73f879604aef8cc03	Fixed in 5f05d83ce689a8930a70dfa73f879604aef8cc03
LinuxLinux	Affected =6.15	Fixed in–

Description

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

References

Community reviews

Loading reviews…