md raid: fix hang when stopping arrays with metadata through dm-raid
- 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 4.15, 4.20, 5.5, 5.11, 5.16, and 4 more
- 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 raid: fix hang when stopping arrays with metadata through dm-raid When using device-mapper's dm-raid target, stopping a RAID array can cause the system to hang under specific conditions. This occurs when: • A dm-raid managed device tree is suspended from top to bottom (the top-level RAID device is suspended first, followed by its underlying metadata and data devices) • The top-level RAID device is then removed Removing the top-level device triggers a hang in the following sequence: the dm-raid destructor calls md_stop(), which tries to flush the write-intent bitmap by writing to the metadata sub-devices. However, these devices are already suspended, making them unable to complete the write-intent operations and causing an indefinite block. Fix: • Prevent bitmap flushing when md_stop() is called from dm-raid destructor context and avoid a quiescing/unquescing cycle which could also cause I/O • Still allow write-intent bitmap flushing when called from dm-raid suspend context This ensures that RAID array teardown can complete successfully even when the underlying devices are in a suspended state. This second patch uses md_is_rdwr() to distinguish between suspend and destructor paths as elaborated on above.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 0dd84b319352bb8ba64752d4e45396d8b13e6018 · fixed in 63054027d95200b04f3cf624faa7817e0555d56a; From 0dd84b319352bb8ba64752d4e45396d8b13e6018 · fixed in 24783dd06de870d646c25207bae186f78195f912; From 0dd84b319352bb8ba64752d4e45396d8b13e6018 · fixed in 338378dfffbdbb8d37a18f0a0c0358812671f91e; From 0dd84b319352bb8ba64752d4e45396d8b13e6018 · fixed in cefcb9297fbdb6d94b61787b4f8d84f55b741470; From 4.14.292 · fixed in 4.15; From 4.19.257 · fixed in 4.20; From 5.4.212 · fixed in 5.5; From 5.10.140 · fixed in 5.11; From 5.15.64 · fixed in 5.16; From 5.19.6 · fixed in 5.20
- Linux Linux
6.0
- KernelLinux
From 6.0.0 · fixed in 6.12.114; From 6.13.0 · fixed in 6.18.16; From 6.19.0 · fixed in 6.19.6