md: suspend array while updating raid_disks via sysfs
- 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 3.5, 3.10, 6.6.160, 6.12.70, 6.18.10
- 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
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: md: suspend array while updating raid_disks via sysfs In raid1_reshape(), freeze_array() is called before modifying the r1bio memory pool (conf->r1bio_pool) and conf->raid_disks, and unfreeze_array() is called after the update is completed. However, freeze_array() only waits until nr_sync_pending and (nr_pending - nr_queued) of all buckets reaches zero. When an I/O error occurs, nr_queued is increased and the corresponding r1bio is queued to either retry_list or bio_end_io_list. As a result, freeze_array() may unblock before these r1bios are released. This can lead to a situation where conf->raid_disks and the mempool have already been updated while queued r1bios, allocated with the old raid_disks value, are later released. Consequently, free_r1bio() may access memory out of bounds in put_all_bios() and release r1bios of the wrong size to the new mempool, potentially causing issues with the mempool as well. Since only normal I/O might increase nr_queued while an I/O error occurs, suspending the array avoids this issue. Note: Updating raid_disks via ioctl SET_ARRAY_INFO already suspends the array. Therefore, we suspend the array when updating raid_disks via sysfs to avoid this issue too.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From e2d59925221cd562e07fee38ec8839f7209ae603 · fixed in 863b9b7be824a6b2c0587532d3ece3022c6dd451; From e2d59925221cd562e07fee38ec8839f7209ae603 · fixed in 165d1359f945b72c5f90088f60d48ff46115269e; From e2d59925221cd562e07fee38ec8839f7209ae603 · fixed in 0107b18cd8ac17eb3e54786adc05a85cdbb6ef22; From e2d59925221cd562e07fee38ec8839f7209ae603 · fixed in 2cc583653bbe050bacd1cadcc9776d39bf449740; From 3.4.59 · fixed in 3.5; From 3.9.7 · fixed in 3.10
- Linux Linux
3.10
- KernelLinux
From 3.10.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.70; From 6.13.0 · fixed in 6.18.10