Kernel crash via unvalidated btrfs root item
Published May 1, 2026 · Updated May 1, 2026
Reachable assertion in Linux Kernel allows local users to crash the kernel by mounting corrupted btrfs metadata during recovery. The btrfs tree checker accepts a root item whose drop_progress.objectid is nonzero while drop_level is zero, so relocation recovery reaches BUG_ON(level == 0) in merge_reloc_root() or btrfs_drop_snapshot(). Exploitation requires local ability to supply and mount malformed btrfs metadata; the bounded consequence is an availability-only kernel crash during mount-time recovery.
Summary
What happened
Reachable assertion in Linux Kernel allows local users to crash the kernel by mounting corrupted btrfs metadata during recovery. The btrfs tree checker accepts a root item whose drop_progress.objectid is nonzero while drop_level is zero, so relocation recovery reaches BUG_ON(level == 0) in merge_reloc_root() or btrfs_drop_snapshot(). Exploitation requires local ability to supply and mount malformed btrfs metadata; the bounded consequence is an availability-only kernel crash during mount-time recovery.
The record
- CVE
- CVE-2026-43046
- Published
- May 1, 2026
- Updated
- May 1, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-617, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2026CVE publishedPublication date reported by the CVE source.
- May 1, 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <295f8075d00442d71dc9ccae421ace1c0d2d9224
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <53ceedd1eb6280ca8359664e0226983eded2ed73
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <850de3d87f4720b71ccdcd44f4aa57e46b53a3f3
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ac68a9a8e481ab1becaed29d6d23087dac3de15d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b17b79ff896305fd74980a5f72afec370ee88ca4
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <bedaf7d0b9d793e116f16b4d9a7dbc94bcc80443
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <de585ee18dd5601745f65a60fef7b7ceebd78c83
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