Kernel crash via subvolume root-read race
Published Apr 3, 2024 · Updated May 23, 2026
Reachable assertion in Linux btrfs allows local users to crash the kernel during concurrent subvolume-creation operations. A back-reference walk can load the new subvolume root and assign its anonymous device number before btrfs_get_new_fs_root consumes a separately preallocated number, causing the !anon_dev assertion in fs/btrfs/disk-io.c to fail. A local user must be able to create a btrfs subvolume and win the concurrent root-read race; success interrupts the entire host rather than only the invoking process.
Summary
What happened
Reachable assertion in Linux btrfs allows local users to crash the kernel during concurrent subvolume-creation operations. A back-reference walk can load the new subvolume root and assign its anonymous device number before btrfs_get_new_fs_root consumes a separately preallocated number, causing the !anon_dev assertion in fs/btrfs/disk-io.c to fail. A local user must be able to create a btrfs subvolume and win the concurrent root-read race; success interrupts the entire host rather than only the invoking process.
The record
- CVE
- CVE-2024-26727
- Published
- Apr 3, 2024
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-617, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 3, 2024CVE publishedPublication date reported by the CVE source.
- May 23, 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=2dfb1e43f57dd3aeaa66f7cf05d068db2d4c8788 <3f5d47eb163bceb1b9e613c9003bae5fefc0046f
- Affected versionversion=2dfb1e43f57dd3aeaa66f7cf05d068db2d4c8788 <5a172344bfdabb46458e03708735d7b1a918c468
- Affected versionversion=2dfb1e43f57dd3aeaa66f7cf05d068db2d4c8788 <66b317a2fc45b2ef66527ee3f8fa08fb5beab88d
- Affected versionversion=2dfb1e43f57dd3aeaa66f7cf05d068db2d4c8788 <833775656d447c545133a744a0ed1e189ce61430
- Affected versionversion=2dfb1e43f57dd3aeaa66f7cf05d068db2d4c8788 <e03ee2fe873eb68c1f9ba5112fee70303ebf9dfb
- Affected versionversion=2dfb1e43f57dd3aeaa66f7cf05d068db2d4c8788 <e31546b0f34af21738c4ceac47d662c00ee6382f
- Affected versionversion=5.8.3 <5.9
- Affected versionversion=5.9
- Affected versionversion=917d608fe375041eb7f29befa6a6d7fd3cf32dde
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
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