UNKNOWN NVD
CVE-2026-90275
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_fro
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.
References
- https://git.kernel.org/stable/c/668d99ba47210ab6ceb18f1cf022c0accca7e3bb
- https://git.kernel.org/stable/c/b6ec4bf1ec4446c0213c08ea493e48e6b83cd1af
- https://git.kernel.org/stable/c/c57ec2749ee03cace564eec7bb37c89dc3d8d47b
- https://git.kernel.org/stable/c/dc386aa0ac0a3ec06c9a3ea9b064b073fb72a916
- https://git.kernel.org/stable/c/f9cdb5bb8efbf401e84d850828271af87e6be2dc
This unknown severity vulnerability was published on 2026-09-17 via NVD.
vulnfeed aggregates 13500 vulnerabilities from NVD, CISA KEV,
Ubuntu, Debian, Red Hat, Kubernetes, Exploit-DB, OSS-Security, GitHub and OpenStack — updated every 4 hours.