md: remove REQ_NOWAIT support from raid1/10/456
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
5.17
|
In the Linux kernel, the following vulnerability has been resolved:
md: remove REQ_NOWAIT support from raid1/10/456
REQ_NOWAIT support in md personalities that can block internally is fundamentally incomplete. While reads can avoid some blocking paths, write requests can still encounter cases where one mirror succeeds while another returns -EAGAIN. At that point md cannot distinguish queue pressure from a real device failure, so it can neither record a bad block nor safely retry the write without REQ_NOWAIT, leaving mirrors with divergent data.
Rather than continue advertising REQ_NOWAIT support for personalities that cannot implement it correctly, remove it from raid1, raid10 and raid456. Keep REQ_NOWAIT for linear and raid0, which only remap bios to their underlying devices; stacked limits will still clear the feature if any component device lacks REQ_NOWAIT support.
From the CVE record · Linux
Linux kernel md RAID1, RAID10 and RAID456 can handle REQ_NOWAIT writes incorrectly. If one mirror completes a write while another returns -EAGAIN, the mirrors can end up with divergent data. The input does not specify an attacker, access requirements or user interaction.
Engineers running Linux kernel md RAID1, RAID10 or RAID456 should check their systems; affected versions are not specified.