md raid: fix hang when stopping arrays with metadata through dm-raid
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
| No fix yet |
| Linux Linux |
|
|
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:
From the CVE record · Linux
The Linux kernel's md raid handling can hang when stopping a RAID array managed through dm-raid. The hang occurs if the device tree is suspended from top to bottom and the top-level RAID device is then removed; the input does not specify an attacker, authentication requirement, or user interaction.
Engineers running Linux kernels with dm-raid-managed RAID arrays should check their installations; affected versions were not provided.