CVE-2025-38095dma-buf: insert memory barrier before updating num_fences
Updated under an hour ago ()
Does this affect you?
It affects Linux and 2 other products. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Modified
- Record last updated
- Oct 15, 2026
- First seen by InfoSec Signals
- Oct 15, 2026
Affected products
Linux Linux linux:linux (from the name) | from a590d0fdbaa56f482ff515e1040b6d9b1b200d63 before 90eb79c4ed98a4e24a62ccf61c199ab0f680fa8f; from a590d0fdbaa56f482ff515e1040b6d9b1b200d63 before d0b7f11dd68b593bd970e5735be00e8d89bace30; from a590d0fdbaa56f482ff515e1040b6d9b1b200d63 before 3becc659f9cb76b481ad1fb71f54d5c8d6332d3f; from a590d0fdbaa56f482ff515e1040b6d9b1b200d63 before c9d2b9a80d06a58f37e0dc8c827075639b443927; from a590d0fdbaa56f482ff515e1040b6d9b1b200d63 before fe1bebd0edb22e3536cbc920ec713331d1367ad4; from a590d0fdbaa56f482ff515e1040b6d9b1b200d63 before 08680c4dadc6e736c75bc2409d833f03f9003c51; from a590d0fdbaa56f482ff515e1040b6d9b1b200d63 before 72c7d62583ebce7baeb61acce6057c361f73be4a | CNA record |
linux linux_kernel linux:linux_kernel | from 5.0 before 5.10.241; from 5.11 before 5.15.192; from 5.16 before 6.1.140; from 6.2 before 6.6.92; from 6.7 before 6.12.30; from 6.13 before 6.14.8; 6.15; 6.15; and 4 more ranges | NVD |
debian debian_linux debian:debian_linux | 11.0 | NVD |
References
- https://git.kernel.org/stable/c/90eb79c4ed98a4e24a62ccf61c199ab0f680fa8fpatch
- https://git.kernel.org/stable/c/d0b7f11dd68b593bd970e5735be00e8d89bace30patch
- https://git.kernel.org/stable/c/3becc659f9cb76b481ad1fb71f54d5c8d6332d3fpatch
- https://git.kernel.org/stable/c/c9d2b9a80d06a58f37e0dc8c827075639b443927patch
- https://git.kernel.org/stable/c/fe1bebd0edb22e3536cbc920ec713331d1367ad4patch
- https://git.kernel.org/stable/c/08680c4dadc6e736c75bc2409d833f03f9003c51patch
- https://git.kernel.org/stable/c/72c7d62583ebce7baeb61acce6057c361f73be4apatch
- https://lists.debian.org/debian-lts-announce/2025/08/msg00010.htmlmailing-list, third-party-advisory
- https://lists.debian.org/debian-lts-announce/2025/10/msg00007.htmlmailing-list, third-party-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.