CVE-2026-90275

CVE CVE-2026-90275EUVD EUVD-2026-81868Published 2026-09-17T16:08:08.000Z

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux b39f35ebe86d88788d85f61e83c81c308cb76727 <b6ec4bf1ec4446c0213c08ea493e48e6b83cd1af; patch: 6.6.157; 6.6; patch: 7.2.6; patch: 6.18.52; b39f35ebe86d88788d85f61e83c81c308cb76727 <f9cdb5bb8efbf401e84d850828271af87e6be2dc; patch: 7.3-rc1; patch: 6.12.110; patch: 0; b39f35ebe86d88788d85f61e83c81c308cb76727 <dc386aa0ac0a3ec06c9a3ea9b064b073fb72a916; b39f35ebe86d88788d85f61e83c81c308cb76727 <c57ec2749ee03cace564eec7bb37c89dc3d8d47b; b39f35ebe86d88788d85f61e83c81c308cb76727 <668d99ba47210ab6ceb18f1cf022c0accca7e3bb

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.