In the Linux kernel, the following vulnerability has been resolved: md/raid10: fix still_degraded being inverted in raid10_sync_request() Commit… (CVE-2026-89558)
A vulnerability in the Linux kernel's md/raid10 subsystem caused an incorrect boolean assignment that led to silent data corruption during device recovery. The issue inverted the 'still_degraded' flag in raid10_sync_request(), causing bitmap-based recovery to skip regions written while the array was degraded. This results in the array being marked as in-sync despite holding stale data. The flaw was introduced by a commit that converted 'still_degraded' from int to bool but inverted its logic. The problem does not affect cloud services and no CVSS score is available.
AI Analysis
Technical Summary
The Linux kernel's md/raid10 component contained a logic error where the 'still_degraded' flag was inverted after being converted from an integer to a boolean in the raid10_sync_request() function. This inversion caused the recovery process to incorrectly clear bitmap bits needed by a still-missing device. Consequently, when the missing device was re-added, its recovery skipped all regions written during the degraded state, leading to silent data corruption as the array was incorrectly marked as in-sync. The issue was identified by comparing it to the correct logic in the raid1 implementation and has been resolved by restoring the correct boolean assignment.
Potential Impact
The vulnerability can cause silent data corruption in RAID10 arrays during device recovery. Specifically, data written while the array was degraded may be skipped during recovery, resulting in stale data being considered valid. This undermines data integrity and can lead to undetected data loss or corruption. There is no indication of active exploitation in the wild.
Mitigation Recommendations
A fix has been implemented to correct the boolean assignment of the 'still_degraded' flag in the Linux kernel's md/raid10 subsystem. Users should apply the official kernel update that includes this fix to prevent silent data corruption during RAID10 recovery. Patch status is not explicitly stated in the input, so users should consult the vendor or kernel mailing lists for the specific fixed kernel versions and apply updates accordingly.
In the Linux kernel, the following vulnerability has been resolved: md/raid10: fix still_degraded being inverted in raid10_sync_request() Commit… (CVE-2026-89558)
Description
A vulnerability in the Linux kernel's md/raid10 subsystem caused an incorrect boolean assignment that led to silent data corruption during device recovery. The issue inverted the 'still_degraded' flag in raid10_sync_request(), causing bitmap-based recovery to skip regions written while the array was degraded. This results in the array being marked as in-sync despite holding stale data. The flaw was introduced by a commit that converted 'still_degraded' from int to bool but inverted its logic. The problem does not affect cloud services and no CVSS score is available.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's md/raid10 component contained a logic error where the 'still_degraded' flag was inverted after being converted from an integer to a boolean in the raid10_sync_request() function. This inversion caused the recovery process to incorrectly clear bitmap bits needed by a still-missing device. Consequently, when the missing device was re-added, its recovery skipped all regions written during the degraded state, leading to silent data corruption as the array was incorrectly marked as in-sync. The issue was identified by comparing it to the correct logic in the raid1 implementation and has been resolved by restoring the correct boolean assignment.
Potential Impact
The vulnerability can cause silent data corruption in RAID10 arrays during device recovery. Specifically, data written while the array was degraded may be skipped during recovery, resulting in stale data being considered valid. This undermines data integrity and can lead to undetected data loss or corruption. There is no indication of active exploitation in the wild.
Mitigation Recommendations
A fix has been implemented to correct the boolean assignment of the 'still_degraded' flag in the Linux kernel's md/raid10 subsystem. Users should apply the official kernel update that includes this fix to prevent silent data corruption during RAID10 recovery. Patch status is not explicitly stated in the input, so users should consult the vendor or kernel mailing lists for the specific fixed kernel versions and apply updates accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-6w6j-fmcg-fgj3
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-89558"]
Threat ID: 6aa4a01155bf5e2cf5a866ae
Added to database: 09/12/2026, 00:42:57 UTC
Last enriched: 09/12/2026, 01:06:58 UTC
Last updated: 09/12/2026, 01:06:58 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.