Data corruption via cleared failed-write bitmap bits
Published Feb 27, 2024 · Updated May 23, 2026
Data corruption in Linux kernel RAID1 arrays using bitmaps allows local users to corrupt mirrored data when a write request fails. The raid1_end_write_request failure path clears the failed I/O's bitmap bits instead of retaining them for retry or marking the request degraded. The condition requires a bitmap-enabled RAID1 array and a failed write; cleared bits can prevent resynchronization from repairing the stale mirror leg.
Summary
What happened
Data corruption in Linux kernel RAID1 arrays using bitmaps allows local users to corrupt mirrored data when a write request fails. The raid1_end_write_request failure path clears the failed I/O's bitmap bits instead of retaining them for retry or marking the request degraded. The condition requires a bitmap-enabled RAID1 array and a failed write; cleared bits can prevent resynchronization from repairing the stale mirror leg.
The record
- CVE
- CVE-2021-46950
- Published
- Feb 27, 2024
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1565.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 27, 2024CVE publishedPublication date reported by the CVE source.
- May 23, 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=1cd972e0a10760a1fa27d9830d78446c891c23b6 <a6e17cab00fc5bf85472434c52ac751426257c6f
- Affected versionversion=344242d50f468a250bf4b6136934392758412ed8
- Affected versionversion=4.14.147 <4.14.233
- Affected versionversion=4.19.77 <4.19.191
- Affected versionversion=5.2.19 <5.3
- Affected versionversion=5.3.4 <5.4
- Affected versionversion=5.4
- Affected versionversion=900c531899f5ee2321bef79e20055787bc73251d <12216d0919b64ee2ea5dc7a50e455670f44383d5
- Affected versionversion=a1f4fcb880988a96c0b2d5c3305ffc4e49eca0ed
- Affected versionversion=eeba6809d8d58908b5ed1b5ceb5fcb09a98a7cad <2417b9869b81882ab90fd5ed1081a1cb2d4db1dd
- Affected versionversion=eeba6809d8d58908b5ed1b5ceb5fcb09a98a7cad <538244fba59fde17186322776247cd9c05be86dd
- Affected versionversion=eeba6809d8d58908b5ed1b5ceb5fcb09a98a7cad <59452e551784b7a57a45d971727e9db63b192515
- Affected versionversion=eeba6809d8d58908b5ed1b5ceb5fcb09a98a7cad <661061a45e32d8b2cc0e306da9f169ad44011382
- Affected versionversion=eeba6809d8d58908b5ed1b5ceb5fcb09a98a7cad <6920cef604fa57f9409e3960413e9cc11f5c5a40
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