Local system crash via Btrfs subvolume race
Published Jan 23, 2024 · Updated Nov 4, 2025
Reachable assertion in the Linux kernel through 6.7.1 allows local users to crash the system during Btrfs subvolume creation. In btrfs_get_root_ref, a back-reference walk can cache the new root and assign an anonymous device before btrfs_get_new_fs_root uses its preallocated device, violating the !anon_dev assertion. A low-privileged user must create a Btrfs subvolume and win this race; the documented consequence is a kernel crash, not data disclosure or modification.
Summary
What happened
Reachable assertion in the Linux kernel through 6.7.1 allows local users to crash the system during Btrfs subvolume creation. In btrfs_get_root_ref, a back-reference walk can cache the new root and assign an anonymous device before btrfs_get_new_fs_root uses its preallocated device, violating the !anon_dev assertion. A low-privileged user must create a Btrfs subvolume and win this race; the documented consequence is a kernel crash, not data disclosure or modification.
The record
- CVE
- CVE-2024-23850
- Published
- Jan 23, 2024
- Updated
- Nov 4, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-617, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 23, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
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