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-90385md/raid1: create serial pool adding rdev to array with serialize_policy=1

Description

In the Linux kernel, the following vulnerability has been resolved: md/raid1: create serial pool adding rdev to array with serialize_policy=1 The following bug has been observed with kernel 7.1.3 after adding a new rdev to an existing RAID1 array with serialize_policy enabled: Oops: 0002 [#1] CPU: 0 UID: 0 PID: 19639 Comm: ext4lazyinit Not tainted 7.1.3-1-default RIP: _raw_spin_lock_irqsave+0x27/0x50 CR2: 0000000000004960 Call Trace: wait_for_serialization+0xb9/0x260 [raid1] raid1_make_request+0x762/0xaff [raid1] md_handle_request+0x1c9/0x2e0 [md_mod] The raid1.c code calls wait_for_serialization() if the MD_SERIALIZE_POLICY is set, and wait_for_serialization assumes that rdev->serial is initialized. Normally this will be the case for arrays that have the serialize_policy sysfs attribute set to 1. But when a new rdev is added to an existing array in bind_rdev_to_array(), the condition at mddev_create_serial_pool() causes creation of rdev->serial to be skipped. Fix it.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 43 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.21% · top 89% of all CVEs (14 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 69b00b5bb23552d43e8bbed73ef6624604bb94a2 – < 6ea458171bed2b706dc7bcd80b15356c0e9ed718
    • affected 69b00b5bb23552d43e8bbed73ef6624604bb94a2 – < 0b187e14dab458d54425fc400f1e1e8d481d9bcf
    • affected 69b00b5bb23552d43e8bbed73ef6624604bb94a2 – < f9e4364449f7ca6917f3599eb32064dba5b7b147
    • affected 69b00b5bb23552d43e8bbed73ef6624604bb94a2 – < 37f11973c3eb72a5eb061082cad529bb6939c24f
    • affected 69b00b5bb23552d43e8bbed73ef6624604bb94a2 – < c02d675e81468003e4f2253b616c53729070d712
    • affected 69b00b5bb23552d43e8bbed73ef6624604bb94a2 – < 140234b2380ffb8ffb0cfc46fee0e822f43adef7
  • Linux · Linux

    • affected 5.6
    • unaffected < 5.6
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .