Kernel state corruption via Btrfs snapshot double free
Published Apr 4, 2024 · Updated Aug 5, 2026
Double free in Btrfs in the Linux kernel allows local users to corrupt anonymous-device allocator state through snapshot creation. During a failed transaction commit, btrfs_get_new_fs_root() frees pending_snapshot->anon_dev without clearing it, and create_snapshot() then frees the same identifier again. Reaching the flaw requires write and execute permission on an owned directory and a locally mounted Btrfs filesystem; the corrupted global ID allocator can alias live filesystems or trigger a kernel panic under panic_on_warn.
Summary
What happened
Double free in Btrfs in the Linux kernel allows local users to corrupt anonymous-device allocator state through snapshot creation. During a failed transaction commit, btrfs_get_new_fs_root() frees pending_snapshot->anon_dev without clearing it, and create_snapshot() then frees the same identifier again. Reaching the flaw requires write and execute permission on an owned directory and a locally mounted Btrfs filesystem; the corrupted global ID allocator can alias live filesystems or trigger a kernel panic under panic_on_warn.
The record
- CVE
- CVE-2024-26792
- Published
- Apr 4, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-415, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 4, 2024CVE 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=3f5d47eb163bceb1b9e613c9003bae5fefc0046f
- Affected versionversion=5.10.210 <5.11
- Affected versionversion=5.15.149 <5.16
- Affected versionversion=5a172344bfdabb46458e03708735d7b1a918c468 <c8ab7521665bd0f8bc4a900244d1d5a7095cc3b9
- Affected versionversion=6.1.79 <6.1.81
- Affected versionversion=6.6.18 <6.6.21
- Affected versionversion=66b317a2fc45b2ef66527ee3f8fa08fb5beab88d <c34adc20b91a8e55e048b18d63f4f4ae003ecf8f
- Affected versionversion=6.7.6 <6.7.9
- Affected versionversion=833775656d447c545133a744a0ed1e189ce61430 <eb3441093aad251418921246fc3b224fd1575701
- Affected versionversion=e03ee2fe873eb68c1f9ba5112fee70303ebf9dfb <e2b54eaf28df0c978626c9736b94f003b523b451
- Affected versionversion=e31546b0f34af21738c4ceac47d662c00ee6382f
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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