CVE-2026-89558
Last modified
CVE-2026-89558 is a critical-severity vulnerability rated 9.8/10 on the CVSS scale. 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.. EPSS estimates a 0.20% chance of exploitation in the next 30 days.
Description
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.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= fe6a19d40ceb44281905485f56dda715e3214e0e, < 9bb8da6ecb330a5b1ac9b96f1e55f134a7aef1d4; >= fe6a19d40ceb44281905485f56dda715e3214e0e, < 0efabe6229dc683dbf6eeebd0f9fddc7971ed420; >= fe6a19d40ceb44281905485f56dda715e3214e0e, < 00449d752bee9c8787f42ea1bf533a9fb17f9b6b; >= fe6a19d40ceb44281905485f56dda715e3214e0e, < 47f1441b281decde6954a2fa82b4131637d685ac |
| Linux | Linux | 6.12 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-89558?
How severe is CVE-2026-89558?
How do I fix CVE-2026-89558?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-89552In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89553In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-89554In the Linux kernel, the following vulnerability has been re…8.2
- CVE-2026-89555In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-89556In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89557In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-89559In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-8956Integer overflow in the Networking: JAR component. This vuln…9.8
- CVE-2026-89560In the Linux kernel, the following vulnerability has been re…8.4
- CVE-2026-89561In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-89562In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-89563In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-89558?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
