DM-RAID1 Error Handling Fix for Unsupported Operations

Publication date: 2026-09-11

Last updated on: 2026-09-11

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: dm-io: report non-retryable errors separatedly The error codes BLK_STS_NOTSUPP and BLK_STS_INVAL should not cause leg failure on dm-raid1. This patch changes the interface to dm-io, so that it reports two error bitmaps - error_bits and unsup_bits. The unsup_bit bitmap tracks BLK_STS_NOTSUPP or BLK_STS_INVAL errors, the error_bits 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 unsup_bits bitmap. This patch (with 62dc37a819a5) fixes misbehavior if the user uses unaligned bio vectors on dm-raid1.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-11

Last Modified

2026-09-11

Generated

2026-09-12

AI Q&A

2026-09-12

EPSS Evaluated

N/A

NVD

CVE-2026-89577

EUVD

EUVD-2026-76489

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability in the Linux kernel involves dm-io error reporting. It separates non-retryable errors (BLK_STS_NOTSUPP and BLK_STS_INVAL) from other errors using two bitmaps: error_bits for general errors and unsup_bits for unsupported/invalid operations. dm-raid1 no longer fails a leg when receiving errors in unsup_bits.

Impact Analysis

This vulnerability primarily affects systems using dm-raid1 with unaligned bio vectors. It could lead to incorrect error handling where unsupported or invalid operations are treated as critical failures, potentially causing data corruption or system instability.

Hi! I’m here to help you understand CVE-2026-89577. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70