md/raid5: fix IO hang with degraded array with llbitmap
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 |
|
|
6.18.146.19.47.0In the Linux kernel, the following vulnerability has been resolved:
md/raid5: fix IO hang with degraded array with llbitmap
When llbitmap bit state is still unwritten, any new write should force rcw, as bitmap_ops->blocks_synced() is checked in handle_stripe_dirtying(). However, later the same check is missing in need_this_block(), causing stripe to deadloop during handling because handle_stripe() will decide to go to handle_stripe_fill(), meanwhile need_this_block() always return 0 and nothing is handled.
From the CVE record · Linux
A missing check in the Linux kernel's md/raid5 code can cause an I/O hang. This can occur when a new write reaches a degraded array using llbitmap while a bitmap bit is still unwritten. The input does not specify an attacker path, authentication requirement, or user-interaction requirement.
Engineers running Linux kernels with md/raid5 degraded arrays using llbitmap should check their systems; affected versions are not specified.