CVE-2026-90275

Unknown

Description

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.

SeverityUnknown
CVSS—
Exploit probability—
ProductLinux
PublishedSep 17, 2026
First seenSep 17, 2026

How to fix

Update
  • Linux Linux668d99ba47210ab6ceb18f1cf022c0accca7e3bb, c57ec2749ee03cace564eec7bb37c89dc3d8d47b, f9cdb5bb8efbf401e84d850828271af87e6be2dc, b6ec4bf1ec4446c0213c08ea493e48e6b83cd1af, dc386aa0ac0a3ec06c9a3ea9b064b073fb72a916 or later

Affected products

ProductAffected versionsFixed in
Linux Linuxb39f35ebe86d88788d85f61e83c81c308cb76727 ≤ v < 668d99ba47210ab6ceb18f1cf022c0accca7e3bb, b39f35ebe86d88788d85f61e83c81c308cb76727 ≤ v < c57ec2749ee03cace564eec7bb37c89dc3d8d47b, b39f35ebe86d88788d85f61e83c81c308cb76727 ≤ v < f9cdb5bb8efbf401e84d850828271af87e6be2dc, b39f35ebe86d88788d85f61e83c81c308cb76727 ≤ v < b6ec4bf1ec4446c0213c08ea493e48e6b83cd1af, b39f35ebe86d88788d85f61e83c81c308cb76727 ≤ v < dc386aa0ac0a3ec06c9a3ea9b064b073fb72a916, 6.6668d99ba47210ab6ceb18f1cf022c0accca7e3bb, c57ec2749ee03cace564eec7bb37c89dc3d8d47b, f9cdb5bb8efbf401e84d850828271af87e6be2dc, b6ec4bf1ec4446c0213c08ea493e48e6b83cd1af, dc386aa0ac0a3ec06c9a3ea9b064b073fb72a916

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.