CVE-2026-89558md/raid10: fix still_degraded being inverted in raid10_sync_request()
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 9.8 CRITICAL (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Sep 13, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from fe6a19d40ceb44281905485f56dda715e3214e0e before 9bb8da6ecb330a5b1ac9b96f1e55f134a7aef1d4; from fe6a19d40ceb44281905485f56dda715e3214e0e before 0efabe6229dc683dbf6eeebd0f9fddc7971ed420; from fe6a19d40ceb44281905485f56dda715e3214e0e before 00449d752bee9c8787f42ea1bf533a9fb17f9b6b; from fe6a19d40ceb44281905485f56dda715e3214e0e before 47f1441b281decde6954a2fa82b4131637d685ac | CNA record |
References
- https://git.kernel.org/stable/c/9bb8da6ecb330a5b1ac9b96f1e55f134a7aef1d4
- https://git.kernel.org/stable/c/0efabe6229dc683dbf6eeebd0f9fddc7971ed420
- https://git.kernel.org/stable/c/00449d752bee9c8787f42ea1bf533a9fb17f9b6b
- https://git.kernel.org/stable/c/47f1441b281decde6954a2fa82b4131637d685ac
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.