# Revert "drm/gem-framebuffer: Use dma_buf from GEM object instance"

CVE record · `CVE-2025-38673`

- **Identifiers:** `CVE-2025-38673`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 22 Aug 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 22 Aug 2025, 16:03 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `cce16fcd7446dcff7480cd9d2b6417075ed81065 to before e31f5a1c2cd38bf977736cdfa79444e19d4005ec` (git)
  - affected: `cce16fcd7446dcff7480cd9d2b6417075ed81065 to before 2712ca878b688682ac2ce02aefc413fc76019cd9` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.15`
  - unaffected: `before 6.15` (semver)
  - unaffected: `6.15.9 to 6.15.*, inclusive` (semver)
  - unaffected: `6.16 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel is affected from version 6.15 until the fixed releases. The dma_buf field of a GEM object can become NULL when user space releases the final GEM handle, causing a NULL-pointer dereference. The source gives few details on what an attacker needs. Upgrade to 6.15.9 or later in the 6.15 series, or to 6.16 or later.

Written 16 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0014, the 3rd percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 22 Aug 2025, 16:03 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2025-38673)
- 22 Aug 2025, 16:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2025-38673)

## Sources

- [CVE List: CVE-2025-38673](https://www.cve.org/CVERecord?id=CVE-2025-38673)
- [NVD: CVE-2025-38673](https://nvd.nist.gov/vuln/detail/CVE-2025-38673)

### References from the CNA

- <https://git.kernel.org/stable/c/e31f5a1c2cd38bf977736cdfa79444e19d4005ec>
- <https://git.kernel.org/stable/c/2712ca878b688682ac2ce02aefc413fc76019cd9>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2025-38673>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2025-38673/>. Everything for agents: <https://agentprime.io/llms.txt>.
