Kernel crash via unordered btrfs work completion
Published Apr 10, 2024 · Updated Aug 5, 2026
Race condition in affected Linux btrfs kernels allows local users to crash the kernel through concurrent compressed writeback. In fs/btrfs/async-thread.c, ordinary bit operations on WORK_DONE_BIT provide no memory ordering, so run_ordered_work can observe async_chunk state before producer writes are visible. A local user needs write access to a mounted btrfs filesystem and can trigger the race with ordinary writes and fsync; the resulting stale or torn state can cause an oops, hang, memory disclosure, or memory corruption.
Summary
What happened
Race condition in affected Linux btrfs kernels allows local users to crash the kernel through concurrent compressed writeback. In fs/btrfs/async-thread.c, ordinary bit operations on WORK_DONE_BIT provide no memory ordering, so run_ordered_work can observe async_chunk state before producer writes are visible. A local user needs write access to a mounted btrfs filesystem and can trigger the race with ordinary writes and fsync; the resulting stale or torn state can cause an oops, hang, memory disclosure, or memory corruption.
The record
- CVE
- CVE-2021-47189
- Published
- Apr 10, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 10, 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=08a9ff3264181986d1d692a4e6fce3669700c9f8 <45da9c1767ac31857df572f0a909fbe88fd5a7e9
- Affected versionversion=08a9ff3264181986d1d692a4e6fce3669700c9f8 <47e6f9f69153247109042010f3a77579e9dc61ff
- Affected versionversion=08a9ff3264181986d1d692a4e6fce3669700c9f8 <637d652d351fd4f263ef302dc52f3971d314e500
- Affected versionversion=08a9ff3264181986d1d692a4e6fce3669700c9f8 <670f6b3867c8f0f11e5097f353b164cecfec6179
- Affected versionversion=08a9ff3264181986d1d692a4e6fce3669700c9f8 <6adbc07ebcaf8bead08b21687d49e0fc94400987
- Affected versionversion=08a9ff3264181986d1d692a4e6fce3669700c9f8 <804a9d239ae9cbe88e861a7cd62319cc6ec7b136
- Affected versionversion=08a9ff3264181986d1d692a4e6fce3669700c9f8 <bd660a20fea3ec60a49709ef5360f145ec0fe779
- Affected versionversion=08a9ff3264181986d1d692a4e6fce3669700c9f8 <ed058d735a70f4b063323f1a7bb33cda0f987513
- Affected versionversion=3.15
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo