md/raid1,raid10: fix bio accounting for split md cloned bios
- 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.6.160, 6.12.114, 6.18.57, 7.1.5
- 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: md/raid1,raid10: fix bio accounting for split md cloned bios Use md_cloned_bio() to control bio accounting instead of relying on r1bio_existed in raid1 or the io_accounting flag in raid10. The previous logic does not reliably reflect whether a bio is an md cloned bio. When a failed bio is split and resubmitted via bio_submit_split_bioset() on the error path, this can lead to either double accounting for md cloned bios, or missing accounting for bios returned from bio_submit_split_bioset() Fix this by using md_cloned_bio() to detect md cloned bios and skip accounting accordingly.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From bb2a9acefaf9ce5bbc1e70f407e34599233d0243 · fixed in 91d0fc000d8cc40fcb4285e6160dd1ce98c56201; From bb2a9acefaf9ce5bbc1e70f407e34599233d0243 · fixed in 235d16ae715104b981a4fbc9434398e3816773b1; From bb2a9acefaf9ce5bbc1e70f407e34599233d0243 · fixed in bcf30e14d2bd509c57e93021b46aedc878896e7b; From bb2a9acefaf9ce5bbc1e70f407e34599233d0243 · fixed in bb8d7ea74206b419aa05d7773a15a923b668c9f0; From bb2a9acefaf9ce5bbc1e70f407e34599233d0243 · fixed in ba976e3501111d11c550848b3b7341a73035f582
- Linux Linux
6.6
- KernelLinux
From 6.6.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.114; From 6.13.0 · fixed in 6.18.57; From 6.19.0 · fixed in 7.1.5