dm-io: report non-retryable errors separatedly
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.50, 7.2.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 5ff3f74e145adc79b49668adb8de276446acf6be · fixed in 49694a363f7ecd5a52d1ea1a13c287ad6d196c35; From 5ff3f74e145adc79b49668adb8de276446acf6be · fixed in 15fc1ec72e1f8089063d298550ada727e18f114a; From 5ff3f74e145adc79b49668adb8de276446acf6be · fixed in 47a5e62f39875f371bded6e34ffb9cf15ccd813d
- Linux Linux
6.18
- KernelLinux
From 6.18.0 · fixed in 6.18.50; From 6.19.0 · fixed in 7.2.4