md/raid10: fix still_degraded being inverted in raid10_sync_request()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.12.109, 6.18.50, 7.2.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: md/raid10: fix still_degraded being inverted in raid10_sync_request() Commit fe6a19d40ceb ("md/md-bitmap: merge md_bitmap_start_sync() into bitmap_operations") converted still_degraded from int to bool, but inverted the assignment in the loop that checks whether the array will still be degraded after the current device is recovered: "still_degraded = 1" became "still_degraded = false". As a result, recovering a device while another mirror is still missing calls md_bitmap_start_sync() with degraded == false, which clears bitmap bits that the still-missing device needs. When that device is re-added, its bitmap-based recovery finds the bits already cleared and skips every region written while the array was degraded, so it is marked In_sync while holding stale data: silent corruption. Reproducer (raid10 near=2, 4 disks, internal bitmap): • fail and remove one disk of each mirror pair • write to the degraded array • re-add both disks and let recovery finish • "check" reports mismatch_cnt=262272 after 256 MiB of degraded writes and file contents differ; the second disk's "recovery" completes in milliseconds because everything is skipped The same conversion in raid1 got it right (still_degraded = true). Restore the correct value.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From fe6a19d40ceb44281905485f56dda715e3214e0e · fixed in 9bb8da6ecb330a5b1ac9b96f1e55f134a7aef1d4; From fe6a19d40ceb44281905485f56dda715e3214e0e · fixed in 0efabe6229dc683dbf6eeebd0f9fddc7971ed420; From fe6a19d40ceb44281905485f56dda715e3214e0e · fixed in 00449d752bee9c8787f42ea1bf533a9fb17f9b6b; From fe6a19d40ceb44281905485f56dda715e3214e0e · fixed in 47f1441b281decde6954a2fa82b4131637d685ac
- Linux Linux
6.12
- KernelLinux
From 6.12.0 · fixed in 6.12.109; From 6.13.0 · fixed in 6.18.50; From 6.19.0 · fixed in 7.2.4