PoC Monitor
← All CVEs
CVE-2026-89558published 11 Sep 2026 19:44 UTCData: JSON · API

Linux

md/raid10: fix still_degraded being inverted in raid10_sync_request()

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS9.8critical · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= fe6a19d40ceb44281905485f56dda715e3214e0e, < 9bb8da6ecb330a5b1ac9b96f1e55f134a7aef1d4
  • >= fe6a19d40ceb44281905485f56dda715e3214e0e, < 0efabe6229dc683dbf6eeebd0f9fddc7971ed420
  • >= fe6a19d40ceb44281905485f56dda715e3214e0e, < 00449d752bee9c8787f42ea1bf533a9fb17f9b6b
  • >= fe6a19d40ceb44281905485f56dda715e3214e0e, < 47f1441b281decde6954a2fa82b4131637d685ac

Fixed in 9bb8da6ecb330a5b1ac9b96f1e55f134a7aef1d4, 0efabe6229dc683dbf6eeebd0f9fddc7971ed420, 00449d752bee9c8787f42ea1bf533a9fb17f9b6b, 47f1441b281decde6954a2fa82b4131637d685ac

Linux Linux
  • 6.12

Fixed in 0, 6.12.109, 6.18.50, 7.2.4, 7.3

Mitigation

Upgrade Linux to 9bb8da6ecb330a5b1ac9b96f1e55f134a7aef1d4 or 0efabe6229dc683dbf6eeebd0f9fddc7971ed420 or 00449d752bee9c8787f42ea1bf533a9fb17f9b6b or 47f1441b281decde6954a2fa82b4131637d685ac or later.

Upgrade Linux to 0 or 6.12.109 or 6.18.50 or 7.2.4 or 7.3 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published11 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.