Kernel crash via reversed btrfs reference arguments
Published Jun 18, 2025 · Updated May 11, 2026
NULL pointer dereference in btrfs in Linux 4.14 and later before branch-specific fixes allows local users to crash the kernel during writeback. btrfs_prelim_ref() passes old and new references in the wrong order, causing trace_btrfs_prelim_ref_insert() to dereference a NULL oldref pointer. Exploitation requires local access, permission to enable btrfs preliminary-reference tracing, and writeback activity; the observed consequence is a kernel oops that interrupts the system.
Summary
What happened
NULL pointer dereference in btrfs in Linux 4.14 and later before branch-specific fixes allows local users to crash the kernel during writeback. btrfs_prelim_ref() passes old and new references in the wrong order, causing trace_btrfs_prelim_ref_insert() to dereference a NULL oldref pointer. Exploitation requires local access, permission to enable btrfs preliminary-reference tracing, and writeback activity; the observed consequence is a kernel oops that interrupts the system.
The record
- CVE
- CVE-2025-38034
- Published
- Jun 18, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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=00142756e1f8015d2f8ce96532d156689db7e448 <0528bba48dce7820d2da72e1a114e1c4552367eb
- Affected versionversion=00142756e1f8015d2f8ce96532d156689db7e448 <137bfa08c6441f324d00692d1e9d22cfd773329b
- Affected versionversion=00142756e1f8015d2f8ce96532d156689db7e448 <5755b6731655e248c4f1d52a2e1b18795b4a2a3a
- Affected versionversion=00142756e1f8015d2f8ce96532d156689db7e448 <7a97f961a568a8f72472dc804af02a0f73152c5f
- Affected versionversion=00142756e1f8015d2f8ce96532d156689db7e448 <7f7c8c03feba5f2454792fab3bb8bd45bd6883f9
- Affected versionversion=00142756e1f8015d2f8ce96532d156689db7e448 <a641154cedf9d69730f8af5d0a901fe86e6486bd
- Affected versionversion=00142756e1f8015d2f8ce96532d156689db7e448 <a876703894a6dd6e8c04b0635d86e9f7a7c81b79
- Affected versionversion=00142756e1f8015d2f8ce96532d156689db7e448 <bc7e0975093567f51be8e1bdf4aa5900a3cf0b1e
- Affected versionversion=4.14
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.
Weakness, pattern, technique
Public exploit references
- Kernel.org btrfs tracepoint reproduction procedureproof of concept · demonstrated
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