Local denial of service via unreleased bcache lock
Published May 9, 2020 · Updated Aug 4, 2024
Denial of service in Linux kernel 5.6.11 and earlier allows local users to hang systems through a failed bcache B-tree coalescing operation. On failure, btree_gc_coalesce reaches out_nocoalesce without releasing new_nodes[i]->write_lock, then deadlocks when that lock is acquired again. The flaw requires local access and an active bcache configuration; successful exploitation hangs kernel storage work and interrupts service.
Summary
What happened
Denial of service in Linux kernel 5.6.11 and earlier allows local users to hang systems through a failed bcache B-tree coalescing operation. On failure, btree_gc_coalesce reaches out_nocoalesce without releasing new_nodes[i]->write_lock, then deadlocks when that lock is acquired again. The flaw requires local access and an active bcache configuration; successful exploitation hangs kernel storage work and interrupts service.
The record
- CVE
- CVE-2020-12771
- Published
- May 9, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-667, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 9, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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