CVE-2026-89558

published 11 Sep 2026 · updated 15 Nov 2026

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

9.8CriticalCVSS 9.8EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel 9bb8da6ecb330a5b1ac9b96f1e55f134a7aef1d4, Kernel 00449d752bee9c8787f42ea1bf533a9fb17f9b6b, Kernel 0efabe6229dc683dbf6eeebd0f9fddc7971ed420 and 4 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=fe6a19d40ceb44281905485f56dda715e3214e0e <9bb8da6ecb330a5b1ac9b96f1e55f134a7aef1d4, >=fe6a19d40ceb44281905485f56dda715e3214e0e <00449d752bee9c8787f42ea1bf533a9fb17f9b6b, >=fe6a19d40ceb44281905485f56dda715e3214e0e <0efabe6229dc683dbf6eeebd0f9fddc7971ed420, >=fe6a19d40ceb44281905485f56dda715e3214e0e <47f1441b281decde6954a2fa82b4131637d685ac, =6.129bb8da6ecb330a5b1ac9b96f1e55f134a7aef1d4, 00449d752bee9c8787f42ea1bf533a9fb17f9b6b, 0efabe6229dc683dbf6eeebd0f9fddc7971ed420, 47f1441b281decde6954a2fa82b4131637d685ac
linux-kernel: Kernel>=6.13.0 <6.18.50, >=6.19.0 <7.2.4, >=6.12.0 <6.12.1096.18.50, 7.2.4, 6.12.109

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-89558 severity on Zeptric[![CVE-2026-89558](https://zeptric.io/badge/cve/CVE-2026-89558.svg)](https://zeptric.io/cve/CVE-2026-89558)