Skip to main content
VulnerabilityPublished Updated

CVE-2026-45888: Linux kernel · md/raid1: fix memory leak in raid1_run()

Affects Linux kernelSource CVE Database V5

0
Compare

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

Data as of 6 Nov 2026, 16:05 UTC

Severity
Low

Rated Low by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in ec10e3dc93994b87adf7c759a4639fe34013989a, c94fd6e8a71efd047ff36930e840f3c25679e136, b37588b0282a2b3cdda9db1d53712745ce66dea0 +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 6 Nov 2026.

What to do

Upgrade Linux kernel to ec10e3dc93994b87adf7c759a4639fe34013989a, c94fd6e8a71efd047ff36930e840f3c25679e136, b37588b0282a2b3cdda9db1d53712745ce66dea0 or 6abc7d5dcf0ee0f85e16e41c87fbd06231f28753.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 97894f7d3c2966164516a8a5109674763d3a55e1, < ec10e3dc93994b87adf7c759a4639fe34013989a
Fixed in
  • ec10e3dc93994b87adf7c759a4639fe34013989a
LinuxLinuxAffected
  • ≥ 97894f7d3c2966164516a8a5109674763d3a55e1, < c94fd6e8a71efd047ff36930e840f3c25679e136
Fixed in
  • c94fd6e8a71efd047ff36930e840f3c25679e136
LinuxLinuxAffected
  • ≥ 97894f7d3c2966164516a8a5109674763d3a55e1, < b37588b0282a2b3cdda9db1d53712745ce66dea0
Fixed in
  • b37588b0282a2b3cdda9db1d53712745ce66dea0
LinuxLinuxAffected
  • ≥ 97894f7d3c2966164516a8a5109674763d3a55e1, < 6abc7d5dcf0ee0f85e16e41c87fbd06231f28753
Fixed in
  • 6abc7d5dcf0ee0f85e16e41c87fbd06231f28753
LinuxLinuxAffected
  • =6.9
Fixed in–

AI-suggested

A fix is available and has been applied in the Linux kernel. Users should update to the fixed versions identified by the commits ec10e3dc93994b87adf7c759a4639fe34013989a, c94fd6e8a71efd047ff36930e840f3c25679e136, b37588b0282a2b3cdda9db1d53712745ce66dea0, and 6abc7d5dcf0ee0f85e16e41c87fbd06231f28753. Applying these updates will resolve the memory leak issue.

Description

A memory leak vulnerability was identified and fixed in the Linux kernel's md/raid1 subsystem within the raid1_run() function. The issue occurs when raid1_set_limits() fails after a thread has been registered by md_register_thread(), but the thread is not properly unregistered, causing a leak of the md_thread structure and associated thread resources. The fix adds a call to md_unregister_thread() in the error path to ensure proper cleanup.

References

Community reviews

Loading reviews…