CVE-2026-64244

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-24. 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

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:

drivers/base/memory: set mem->altmap after successful device registration

If __add_memory_block() fails at xa_store() (under memory pressure for example), device_unregister() is called, which eventually triggers memory_block_release() with mem->altmap still set, causing a WARN_ON(mem->altmap). This was triggered by modifying virtio-mem driver.

Fix this by delaying the assignment of mem->altmap until after __add_memory_block() has succeeded.

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 24, 2026

Last Modified

August 17, 2026

Advisory Details (6)

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

drivers/base/memory: set mem->altmap after successful device registration - kernel/git/stable/linux.git - Linux kernel stable tree

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

drivers/base/memory: set mem->altmap after successful device registration - kernel/git/stable/linux.git - Linux kernel stable tree

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

drivers/base/memory: set mem->altmap after successful device registration - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/802e113cf120df7208e4c7e604950a85e87120a8
generic

drivers/base/memory: set mem->altmap after successful device registration - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6c25bf4e44a2b6a14332f952bba0974521f5b72d
generic

drivers/base/memory: set mem->altmap after successful device registration - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/22dc0d042f02ce82aa61422ea5f232628bfd9e9c
generic

drivers/base/memory: set mem->altmap after successful device registration - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/059ac6252a63edf1cea79bf30bd860a8c264b62c

Vendor Advisories for CVE-2026-64244(2)

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

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (29 versions)6.12.95-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (143 versions)7.0.14-1—

Data Freshness Timeline

(refreshed 22× in last 7d / 68× 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.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-30 00:18 UTCEG score recompute
  3. 2026-08-30 00:18 UTCVendor advisory
  4. 2026-08-30 00:18 UTCGHSA enrichment
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-27 21:06 UTCEG score recompute
  7. 2026-08-27 21:06 UTCVendor advisory
  8. 2026-08-27 21:06 UTCGHSA enrichment
  9. 2026-08-26 19:52 UTCEG score recompute
  10. 2026-08-26 19:52 UTCVendor advisory
  11. 2026-08-26 19:52 UTCGHSA enrichment
  12. 2026-08-26 14:47 UTCEPSS rescore
  13. 2026-08-25 18:47 UTCEG score recompute
  14. 2026-08-25 18:47 UTCVendor advisory
  15. 2026-08-25 18:47 UTCGHSA enrichment
  16. 2026-08-25 13:49 UTCEPSS rescore
  17. 2026-08-24 19:03 UTCEG score recompute
  18. 2026-08-24 19:03 UTCVendor advisory
  19. 2026-08-24 19:03 UTCGHSA enrichment
  20. 2026-08-23 19:18 UTCEG score recompute
  21. 2026-08-23 19:18 UTCVendor advisory
  22. 2026-08-23 19:18 UTCGHSA enrichment
  23. 2026-08-23 00:19 UTCEPSS rescore
  24. 2026-08-22 19:33 UTCEG score recompute
  25. 2026-08-22 19:33 UTCVendor advisory
Show 61 more
  1. 2026-08-22 19:33 UTCGHSA enrichment
  2. 2026-08-21 23:49 UTCEPSS rescore
  3. 2026-08-21 19:48 UTCEG score recompute
  4. 2026-08-21 19:48 UTCGHSA enrichment
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-20 20:03 UTCVendor advisory
  7. 2026-08-20 20:03 UTCGHSA enrichment
  8. 2026-08-19 20:18 UTCEG score recompute
  9. 2026-08-19 20:18 UTCVendor advisory
  10. 2026-08-19 20:18 UTCGHSA enrichment
  11. 2026-08-19 17:04 UTCEPSS rescore
  12. 2026-08-18 19:12 UTCEG score recompute
  13. 2026-08-18 19:12 UTCVendor advisory
  14. 2026-08-18 19:12 UTCGHSA enrichment
  15. 2026-08-18 13:48 UTCEPSS rescore
  16. 2026-08-17 19:27 UTCEG score recompute▲ 5.50
  17. 2026-08-17 19:27 UTCVendor advisory
  18. 2026-08-17 19:27 UTCGHSA enrichment
  19. 2026-08-17 19:27 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-17 05:25 UTCNVD update
  22. 2026-08-17 05:22 UTCVendor advisory
  23. 2026-08-17 05:22 UTCGHSA enrichment
  24. 2026-08-17 05:05 UTCMITRE cvelistV5
  25. 2026-08-16 14:56 UTCEPSS rescore
  26. 2026-08-15 01:30 UTCEPSS rescore
  27. 2026-08-14 11:13 UTCGHSA enrichment
  28. 2026-08-13 22:00 UTCEPSS rescore
  29. 2026-08-12 13:51 UTCEPSS rescore
  30. 2026-08-11 12:16 UTCGHSA enrichment
  31. 2026-08-11 00:00 UTCEPSS rescore
  32. 2026-08-08 16:37 UTCEPSS rescore
  33. 2026-08-08 13:20 UTCGHSA enrichment
  34. 2026-08-06 13:47 UTCEPSS rescore
  35. 2026-08-05 19:17 UTCEPSS rescore
  36. 2026-08-05 19:17 UTCEPSS rescore
  37. 2026-08-05 14:23 UTCGHSA enrichment
  38. 2026-08-04 15:10 UTCEPSS rescore
  39. 2026-08-04 10:39 UTCEPSS rescore
  40. 2026-08-03 10:36 UTCEPSS rescore
  41. 2026-08-02 14:13 UTCGHSA enrichment
  42. 2026-08-02 02:27 UTCEPSS rescore
  43. 2026-08-01 04:16 UTCEPSS rescore
  44. 2026-07-30 16:28 UTCEPSS rescore
  45. 2026-07-30 15:16 UTCEG score recompute
  46. 2026-07-30 15:16 UTCGHSA enrichment
  47. 2026-07-30 01:30 UTCEPSS rescore
  48. 2026-07-30 01:30 UTCEPSS rescore
  49. 2026-07-29 01:55 UTCEG score recompute
  50. 2026-07-29 01:54 UTCGHSA enrichment
  51. 2026-07-28 15:37 UTCEPSS rescore
  52. 2026-07-27 14:14 UTCEPSS rescore
  53. 2026-07-26 14:54 UTCEPSS rescore
  54. 2026-07-26 14:54 UTCEPSS rescore
  55. 2026-07-26 02:57 UTCEG score recompute
  56. 2026-07-26 02:57 UTCGHSA enrichment
  57. 2026-07-25 14:18 UTCEPSS rescore
  58. 2026-07-25 14:18 UTCEPSS rescore
  59. 2026-07-24 16:31 UTCNVD update
  60. 2026-07-24 15:42 UTCEG score recompute
  61. 2026-07-24 15:41 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-64244?
CVE-2026-64244 is a medium vulnerability published on July 24, 2026. In the Linux kernel, the following vulnerability has been resolved: drivers/base/memory: set mem->altmap after successful device registration If addmemoryblock() fails at xa_store() (under memory pressure for example), device_unregister() is called, which eventually triggers memoryblockrelease()…
When was CVE-2026-64244 disclosed?
CVE-2026-64244 was first published in the National Vulnerability Database on July 24, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64244 actively exploited?
CVE-2026-64244 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-64244?
CVE-2026-64244 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64244?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64244, 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-64244

Explore →

Is Your Infrastructure Affected by CVE-2026-64244?

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

Start Free Scan →Browse All CVEs