md: Don't ignore read-only array in md_check_recovery()
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
md: Don't ignore read-only array in md_check_recovery()
Usually if the array is not read-write, md_check_recovery() won't register new sync_thread in the first place. And if the array is read-write and sync_thread is registered, md_set_readonly() will unregister sync_thread before setting the array read-only. md/raid follow this behavior hence there is no problem.
After commit f52f5c71f3d4 ("md: fix stopping sync thread"), following hang can be triggered by test shell/integrity-caching.sh:
1) array is read-only. dm-raid update super block: rs_update_sbs ro = mddev->ro mddev->ro = 0 -> set array read-write md_update_sb
2) register new sync thread concurrently.
3) dm-raid set array back to read-only: rs_update_sbs mddev->ro = ro
4) stop the array: raid_dtr md_stop stop_sync_thread set_bit(MD_RECOVERY_INTR, &mddev->recovery); md_wakeup_thread_directly(mddev->sync_thread); wait_event(..., !test_bit(MD_RECOVERY_RUNNING, &mddev->recovery))
From the CVE record · Linux
A race in Linux kernel md recovery handling can leave a sync thread registered after dm-raid sets an array back to read-only. If the thread is registered concurrently with that transition, stopping the array can hang. The input does not establish an attacker path, authentication requirement, or network exposure.
Engineers running Linux kernel systems that use dm-raid should check their kernel versions against the vendor advisory; affected versions are not specified in the input.