md/raid1: don't set array_frozen in raid1_takeover()

Summary

In the Linux kernel, the following vulnerability has been resolved: md/raid1: don't set array_frozen in raid1_takeover() raid1_takeover() sets conf->array_frozen = 1 on the newly-allocated r1conf and nothing ever clears it, so every I/O to the array stalls permanently once _wait_barrier() sees it stuck at 1. This used to be harmless: level_store() called mddev_resume() right after pers->run(), which called raid1_quiesce(mddev, 0) and cleared array_frozen back to 0 regardless of what raid1_takeover() set. Commit b39f35ebe86d ("md: don't quiesce in mddev_suspend()") removed that quiesce(mddev, 0) call, so the pre-set now sticks. setup_conf() already zero-initializes the new r1conf via kzalloc, so just don't set array_frozen here. Same class of bug as commit 892da88d1cd9 ("md/raid10: fix a 'conf->barrier' leakage in raid10_takeover()"), also triggered by b39f35ebe86d.

Timeline

1. Sep 17, 2026, 4:08 PM UTCCVE published
2. Oct 19, 2026, 9:00 AM UTCRecord last updated

Affected versions

• Linux Linux

  From b39f35ebe86d88788d85f61e83c81c308cb76727 · fixed in 668d99ba47210ab6ceb18f1cf022c0accca7e3bb; From b39f35ebe86d88788d85f61e83c81c308cb76727 · fixed in c57ec2749ee03cace564eec7bb37c89dc3d8d47b; From b39f35ebe86d88788d85f61e83c81c308cb76727 · fixed in f9cdb5bb8efbf401e84d850828271af87e6be2dc; From b39f35ebe86d88788d85f61e83c81c308cb76727 · fixed in b6ec4bf1ec4446c0213c08ea493e48e6b83cd1af; From b39f35ebe86d88788d85f61e83c81c308cb76727 · fixed in dc386aa0ac0a3ec06c9a3ea9b064b073fb72a916

• Linux Linux

  6.6

• KernelLinux

  From 6.6.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6

References 5