CVE-2026-64180

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 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

A fix is available — apply it.

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

mm/memory_hotplug: fix memory block reference leak on remove

Patch series "mm: Fix memory block leaks and locking", v2.

This series fixes two memory block device reference leaks and one locking issue around the per-memory_block hwpoison counter.

This patch (of 2):

remove_memory_blocks_and_altmaps() looks up each memory block with find_memory_block(), which acquires a reference to the memory block device.

That reference is never dropped on this path, resulting in a leaked device reference when removing memory blocks and their altmaps. Drop the reference after retrieving mem->altmap and clearing mem->altmap, before removing the memory block device.

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
2%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 12, 2026

Advisory Details (4)

Auto-updated Aug 12, 2026
No patch confirmed yet.
generic

mm/memory_hotplug: fix memory block reference leak on remove - kernel/git/stable/linux.git - Linux kernel stable tree

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

mm/memory_hotplug: fix memory block reference leak on remove - kernel/git/stable/linux.git - Linux kernel stable tree

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

mm/memory_hotplug: fix memory block reference leak on remove - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/93866f55f7e292fe3d47d36c9efe5ee10213a06b
generic

mm/memory_hotplug: fix memory block reference leak on remove - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/09ce923071e7852ece60d7368e05249bf32c7967

Vendor Advisories for CVE-2026-64180(1)

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

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-18ubuntu
ubuntulinux-virtual-6.8 (6.8.0-139.139) @ noble2026-09-18ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1067.75) @ noble2026-09-18ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-18ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-18ubuntu

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.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (141 versions)7.0.12-1—

All Vendor Advisories

(8)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 12× in last 7d / 72× 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 970 total refreshes for this CVE.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-64180?
CVE-2026-64180 is a medium vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: mm/memory_hotplug: fix memory block reference leak on remove Patch series "mm: Fix memory block leaks and locking", v2. This series fixes two memory block device reference leaks and one locking issue around the per-memory_block…
When was CVE-2026-64180 disclosed?
CVE-2026-64180 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64180 actively exploited?
CVE-2026-64180 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 98.3% of all scored CVEs.
What is the CVSS score of CVE-2026-64180?
CVE-2026-64180 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64180?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64180, 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-64180

Explore →

Is Your Infrastructure Affected by CVE-2026-64180?

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

Start Free Scan →Browse All CVEs