Local crash via misordered dma-buf fence publication
Published Jul 3, 2025 · Updated Aug 5, 2026
NULL pointer dereference in affected Linux kernel builds allows local users to crash the system via concurrent dma-buf fence operations. In drivers/dma-buf/dma-resv.c, smp_store_mb() publishes num_fences before the intended memory barrier, so lockless readers can observe the count before its fence pointer is initialized. A low-privileged local process must race dma-buf fence import against export or synchronization operations; a successful race causes an availability-only kernel crash.
Summary
What happened
NULL pointer dereference in affected Linux kernel builds allows local users to crash the system via concurrent dma-buf fence operations. In drivers/dma-buf/dma-resv.c, smp_store_mb() publishes num_fences before the intended memory barrier, so lockless readers can observe the count before its fence pointer is initialized. A low-privileged local process must race dma-buf fence import against export or synchronization operations; a successful race causes an availability-only kernel crash.
The record
- CVE
- CVE-2025-38095
- Published
- Jul 3, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 3, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.0
- Affected versionversion=a590d0fdbaa56f482ff515e1040b6d9b1b200d63 <08680c4dadc6e736c75bc2409d833f03f9003c51
- Affected versionversion=a590d0fdbaa56f482ff515e1040b6d9b1b200d63 <3becc659f9cb76b481ad1fb71f54d5c8d6332d3f
- Affected versionversion=a590d0fdbaa56f482ff515e1040b6d9b1b200d63 <72c7d62583ebce7baeb61acce6057c361f73be4a
- Affected versionversion=a590d0fdbaa56f482ff515e1040b6d9b1b200d63 <90eb79c4ed98a4e24a62ccf61c199ab0f680fa8f
- Affected versionversion=a590d0fdbaa56f482ff515e1040b6d9b1b200d63 <c9d2b9a80d06a58f37e0dc8c827075639b443927
- Affected versionversion=a590d0fdbaa56f482ff515e1040b6d9b1b200d63 <d0b7f11dd68b593bd970e5735be00e8d89bace30
- Affected versionversion=a590d0fdbaa56f482ff515e1040b6d9b1b200d63 <fe1bebd0edb22e3536cbc920ec713331d1367ad4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo