CVE-2026-89577: dm-io: report non-retryable errors separatedly
In the Linux kernel, the following vulnerability has been resolved:
dm-io: report non-retryable errors separatedly
The error codes BLKSTSNOTSUPP and BLKSTSINVAL should not cause leg failure on dm-raid1. This patch changes the interface to dm-io, so that it reports two error bitmaps - errorbits and unsupbits. The unsupbit bitmap tracks BLKSTSNOTSUPP or BLKSTSINVAL errors, the errorbits bitmap tracks all the other errors.
dm-raid1 is changed so that it won't fail a leg if it receives an error in the unsupbits bitmap.
This patch (with 62dc37a819a5) fixes misbehavior if the user uses unaligned bio vectors on dm-raid1.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch 62dc37a819a5 - Configuration
Apply the dm-io interface change so that the unsup_bits bitmap tracks BLK_STS_NOTSUPP and BLK_STS_INVAL errors, while error_bits tracks all other errors, and dm-io reports non-retryable errors separately.
Linux kernel dm-io (device mapper) error_bits vs unsup_bits tracking for BLK_STS_NOTSUPP and BLK_STS_INVAL = BLK_STS_NOTSUPP/BLK_STS_INVAL -> unsup_bits; all other errors -> error_bits - Configuration
Update dm-raid1 logic so it will not fail a leg/failure on dm-raid1 when it receives BLK_STS_NOTSUPP or BLK_STS_INVAL errors that are recorded in the unsup_bits bitmap.
Linux kernel dm-raid1 LEG failure behavior on unsup errors = do not fail the LAG/LEG if dm-raid1 receives an error in unsup_bits bitmap