Kernel crash via failed Btrfs device addition
Published Sep 25, 2026 · Updated Sep 25, 2026
Use-after-free in Linux Btrfs allows local users to crash the kernel by provoking failure while adding a writable device to a seed filesystem. The btrfs_init_new_device() error path frees the new device without removing post_commit_list from the transaction dev_update_list, leaving a dangling list entry. Triggering the demonstrated crash requires local device-management privileges, a seed filesystem, and an induced failure after metadata-chunk creation.
Summary
What happened
Use-after-free in Linux Btrfs allows local users to crash the kernel by provoking failure while adding a writable device to a seed filesystem. The btrfs_init_new_device() error path frees the new device without removing post_commit_list from the transaction dev_update_list, leaving a dangling list entry. Triggering the demonstrated crash requires local device-management privileges, a seed filesystem, and an induced failure after metadata-chunk creation.
The record
- CVE
- CVE-2026-98091
- Published
- Sep 25, 2026
- Updated
- Sep 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 25, 2026CVE publishedPublication date reported by the CVE source.
- Sep 25, 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=5.2
- Affected versionversion=bbbf7243d62d8be73b7ef60721c127b36b2d523e <0ea6814bc0ff7cff443241bd34db9f0f828f3190
- Affected versionversion=bbbf7243d62d8be73b7ef60721c127b36b2d523e <8b001df2b37ca022f710f3254fbb0bcd6d9e1bed
- Affected versionversion=bbbf7243d62d8be73b7ef60721c127b36b2d523e <c93b3c43df561cd9f592cee20ae058b563f9e5b6
- Affected versionversion=bbbf7243d62d8be73b7ef60721c127b36b2d523e <e9e7e37afa85db770e6084360b21a21a8b3a583f
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started