Skip to main content
VulnerabilityPublished Updated

CVE-2026-90385: Linux kernel · md/raid1: create serial pool adding rdev to array with serialize_policy=1

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in f9e4364449f7ca6917f3599eb32064dba5b7b147 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:07 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in f9e4364449f7ca6917f3599eb32064dba5b7b147, c02d675e81468003e4f2253b616c53729070d712, 140234b2380ffb8ffb0cfc46fee0e822f43adef7 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 69b00b5bb23552d43e8bbed73ef6624604bb94a2, < f9e4364449f7ca6917f3599eb32064dba5b7b147
Fixed in
  • f9e4364449f7ca6917f3599eb32064dba5b7b147
LinuxLinuxAffected
  • ≥ 69b00b5bb23552d43e8bbed73ef6624604bb94a2, < c02d675e81468003e4f2253b616c53729070d712
Fixed in
  • c02d675e81468003e4f2253b616c53729070d712
LinuxLinuxAffected
  • ≥ 69b00b5bb23552d43e8bbed73ef6624604bb94a2, < 140234b2380ffb8ffb0cfc46fee0e822f43adef7
Fixed in
  • 140234b2380ffb8ffb0cfc46fee0e822f43adef7
LinuxLinuxAffected
  • ≥ 69b00b5bb23552d43e8bbed73ef6624604bb94a2, < 37f11973c3eb72a5eb061082cad529bb6939c24f
Fixed in
  • 37f11973c3eb72a5eb061082cad529bb6939c24f
LinuxLinuxAffected
  • ≥ 69b00b5bb23552d43e8bbed73ef6624604bb94a2, < 0b187e14dab458d54425fc400f1e1e8d481d9bcf
Fixed in
  • 0b187e14dab458d54425fc400f1e1e8d481d9bcf
LinuxLinuxAffected
  • =5.6
Fixed in–

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.

References

Community reviews

Loading reviews…