Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-90275md/raid1: don't set array_frozen in raid1_takeover()

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 32 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected b39f35ebe86d88788d85f61e83c81c308cb76727 – < 668d99ba47210ab6ceb18f1cf022c0accca7e3bb
    • affected b39f35ebe86d88788d85f61e83c81c308cb76727 – < c57ec2749ee03cace564eec7bb37c89dc3d8d47b
    • affected b39f35ebe86d88788d85f61e83c81c308cb76727 – < f9cdb5bb8efbf401e84d850828271af87e6be2dc
    • affected b39f35ebe86d88788d85f61e83c81c308cb76727 – < b6ec4bf1ec4446c0213c08ea493e48e6b83cd1af
    • affected b39f35ebe86d88788d85f61e83c81c308cb76727 – < dc386aa0ac0a3ec06c9a3ea9b064b073fb72a916
  • Linux · Linux

    • affected 6.6
    • unaffected < 6.6
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-90275 badge
[![CVE-2026-90275](https://cveledger.app/badge/CVE-2026-90275.svg)](https://cveledger.app/cve/CVE-2026-90275)

Record last updated .