CVE-2026-45888

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-27. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

md/raid1: fix memory leak in raid1_run()

raid1_run() calls setup_conf() which registers a thread via md_register_thread(). If raid1_set_limits() fails, the previously registered thread is not unregistered, resulting in a memory leak of the md_thread structure and the thread resource itself.

Add md_unregister_thread() to the error path to properly cleanup the thread, which aligns with the error handling logic of other paths in this function.

Compile tested only. Issue found using a prototype static analysis tool and code review.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 25, 2026

Advisory Details (4)

Auto-updated Jun 25, 2026
No patch confirmed yet.
generic

md/raid1: fix memory leak in raid1_run() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ec10e3dc93994b87adf7c759a4639fe34013989a
generic

md/raid1: fix memory leak in raid1_run() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c94fd6e8a71efd047ff36930e840f3c25679e136
generic

md/raid1: fix memory leak in raid1_run() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b37588b0282a2b3cdda9db1d53712745ce66dea0
generic

md/raid1: fix memory leak in raid1_run() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6abc7d5dcf0ee0f85e16e41c87fbd06231f28753

Vendor Advisories for CVE-2026-45888(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.12.75—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (103 versions)6.18.14-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 185 total refreshes for this CVE.

  1. 2026-09-20 20:15 UTCEPSS rescore
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 19:31 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-14 09:08 UTCEG score recompute
  7. 2026-09-14 09:08 UTCGHSA enrichment
  8. 2026-09-13 16:47 UTCEPSS rescore
  9. 2026-09-13 04:09 UTCOSV refresh
  10. 2026-09-12 15:01 UTCEPSS rescore
  11. 2026-09-11 14:53 UTCEPSS rescore
  12. 2026-09-11 09:37 UTCEPSS rescore
  13. 2026-09-10 09:34 UTCEPSS rescore
  14. 2026-09-08 22:00 UTCEPSS rescore
  15. 2026-09-07 16:01 UTCEPSS rescore
  16. 2026-09-06 13:47 UTCEPSS rescore
  17. 2026-09-04 05:06 UTCEPSS rescore
  18. 2026-09-02 14:12 UTCEPSS rescore
  19. 2026-09-01 13:54 UTCEPSS rescore
  20. 2026-08-30 19:17 UTCEPSS rescore
  21. 2026-08-30 01:22 UTCEPSS rescore
  22. 2026-08-28 21:41 UTCEPSS rescore
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-25 13:49 UTCEPSS rescore
Show 75 more
  1. 2026-08-25 05:47 UTCEG score recompute
  2. 2026-08-25 05:47 UTCGHSA enrichment
  3. 2026-08-23 15:34 UTCEG score recompute
  4. 2026-08-23 15:34 UTCGHSA enrichment
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-21 23:49 UTCEPSS rescore
  7. 2026-08-21 20:54 UTCEG score recompute
  8. 2026-08-21 20:54 UTCGHSA enrichment
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-20 17:42 UTCEG score recompute
  11. 2026-08-20 17:42 UTCGHSA enrichment
  12. 2026-08-19 17:04 UTCEPSS rescore
  13. 2026-08-18 13:48 UTCEPSS rescore
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 09:21 UTCEG score recompute
  16. 2026-08-17 09:21 UTCGHSA enrichment
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 05:30 UTCEG score recompute
  19. 2026-08-16 05:30 UTCGHSA enrichment
  20. 2026-08-16 02:14 UTCEPSS rescore
  21. 2026-08-15 03:33 UTCEG score recompute
  22. 2026-08-15 03:33 UTCGHSA enrichment
  23. 2026-08-15 01:30 UTCEPSS rescore
  24. 2026-08-14 01:35 UTCEG score recompute
  25. 2026-08-14 01:35 UTCGHSA enrichment
  26. 2026-08-13 22:00 UTCEPSS rescore
  27. 2026-08-12 13:51 UTCEPSS rescore
  28. 2026-08-12 10:43 UTCEG score recompute
  29. 2026-08-12 10:43 UTCGHSA enrichment
  30. 2026-08-11 08:23 UTCEG score recompute
  31. 2026-08-11 08:23 UTCGHSA enrichment
  32. 2026-08-11 00:00 UTCEPSS rescore
  33. 2026-08-10 06:20 UTCEG score recompute
  34. 2026-08-10 06:20 UTCGHSA enrichment
  35. 2026-08-09 13:46 UTCEPSS rescore
  36. 2026-08-09 04:24 UTCEG score recompute
  37. 2026-08-09 04:24 UTCGHSA enrichment
  38. 2026-08-08 16:37 UTCEPSS rescore
  39. 2026-08-08 02:27 UTCEG score recompute
  40. 2026-08-08 02:27 UTCGHSA enrichment
  41. 2026-08-07 00:31 UTCEG score recompute
  42. 2026-08-07 00:31 UTCGHSA enrichment
  43. 2026-08-06 13:47 UTCEPSS rescore
  44. 2026-08-05 20:56 UTCEG score recompute
  45. 2026-08-05 20:56 UTCGHSA enrichment
  46. 2026-08-05 19:17 UTCEPSS rescore
  47. 2026-08-04 15:10 UTCEPSS rescore
  48. 2026-08-04 10:39 UTCEPSS rescore
  49. 2026-08-03 19:39 UTCEG score recompute
  50. 2026-08-03 19:39 UTCGHSA enrichment
  51. 2026-08-03 10:36 UTCEPSS rescore
  52. 2026-08-02 17:42 UTCEG score recompute
  53. 2026-08-02 17:42 UTCGHSA enrichment
  54. 2026-08-02 02:27 UTCEPSS rescore
  55. 2026-08-01 15:45 UTCEG score recompute
  56. 2026-08-01 15:45 UTCGHSA enrichment
  57. 2026-08-01 04:16 UTCEPSS rescore
  58. 2026-07-31 08:04 UTCEG score recompute
  59. 2026-07-31 08:04 UTCGHSA enrichment
  60. 2026-07-30 16:28 UTCEPSS rescore
  61. 2026-07-30 01:30 UTCEPSS rescore
  62. 2026-07-29 15:55 UTCEG score recompute
  63. 2026-07-29 15:55 UTCGHSA enrichment
  64. 2026-07-28 15:36 UTCEPSS rescore
  65. 2026-07-27 14:13 UTCEPSS rescore
  66. 2026-07-27 12:21 UTCEG score recompute
  67. 2026-07-27 12:21 UTCGHSA enrichment
  68. 2026-07-26 14:54 UTCEPSS rescore
  69. 2026-07-26 14:54 UTCEPSS rescore
  70. 2026-07-26 06:12 UTCOSV refresh
  71. 2026-07-25 14:18 UTCEPSS rescore
  72. 2026-07-24 14:17 UTCEPSS rescore
  73. 2026-07-23 14:18 UTCEPSS rescore
  74. 2026-07-23 03:16 UTCEG score recompute
  75. 2026-07-22 14:08 UTCEPSS rescore

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-45888?
CVE-2026-45888 is a medium vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: md/raid1: fix memory leak in raid1_run() raid1run() calls setupconf() which registers a thread via mdregisterthread(). If raid1setlimits() fails, the previously registered thread is not unregistered, resulting in a memory leak of…
When was CVE-2026-45888 disclosed?
CVE-2026-45888 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45888 actively exploited?
CVE-2026-45888 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.4% of all scored CVEs.
What is the CVSS score of CVE-2026-45888?
CVE-2026-45888 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-45888?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45888, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45888

Explore →

Is Your Infrastructure Affected by CVE-2026-45888?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs