Local kernel deadlock via locked buffer release
Published Mar 23, 2022 · Updated Aug 3, 2024
Improper locking in Linux kernel 5.4 through 5.15-rc5 allows local users to hang or crash the system through Btrfs error handling. In btrfs_alloc_tree_block(), failure after btrfs_init_new_buffer() frees the newly allocated extent buffer without first releasing its tree lock. Local access to a Btrfs filesystem and a later allocation or delayed-reference failure are required; the bounded consequence is a kernel deadlock or crash.
Summary
What happened
Improper locking in Linux kernel 5.4 through 5.15-rc5 allows local users to hang or crash the system through Btrfs error handling. In btrfs_alloc_tree_block(), failure after btrfs_init_new_buffer() frees the newly allocated extent buffer without first releasing its tree lock. Local access to a Btrfs filesystem and a later allocation or delayed-reference failure are required; the bounded consequence is a kernel deadlock or crash.
The record
- CVE
- CVE-2021-4149
- Published
- Mar 23, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-667, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 23, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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=kernel 5.15 rc6
What conditions does exploitation require?
What is affected?
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
- Btrfs ENOMEM fault-injection reproducerproof of concept · demonstrated
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