CVE-2026-64182

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:

drivers/base/memory: fix memory block reference leak in poison accounting

memblk_nr_poison_inc() and memblk_nr_poison_sub() look up a memory block via find_memory_block_by_id(), which acquires a reference to the memory block device.

Both helpers use the returned memory block without dropping that reference, leaking the device reference on each successful lookup. Drop the reference after updating nr_hwpoison.

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

Advisory Details (5)

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

drivers/base/memory: fix memory block reference leak in poison accounting - kernel/git/stable/linux.git - Linux kernel stable tree

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

drivers/base/memory: fix memory block reference leak in poison accounting - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8502e2c2d0633f99d94d22ae8dabc10caae1fc2a
generic

drivers/base/memory: fix memory block reference leak in poison accounting - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/686b4283f82cd630fafd7ca9b03dfc080b3ec8fa
generic

drivers/base/memory: fix memory block reference leak in poison accounting - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/24840b3139d7415144b81e4f9f4c44670d15bed9
generic

drivers/base/memory: fix memory block reference leak in poison accounting - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/03a2cc1756a0570f887d624cd6c535ea0cbd4951

Vendor Advisories for CVE-2026-64182(1)

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

Patch Availability(5)

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 (138 versions)7.0.12-1

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 17× in last 7d / 79× 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 967 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64182?
CVE-2026-64182 is a medium vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: drivers/base/memory: fix memory block reference leak in poison accounting memblknrpoisoninc() and memblknrpoisonsub() look up a memory block via findmemoryblockbyid(), which acquires a reference to the memory block device. Both…
When was CVE-2026-64182 disclosed?
CVE-2026-64182 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64182 actively exploited?
CVE-2026-64182 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.4% of all scored CVEs.
What is the CVSS score of CVE-2026-64182?
CVE-2026-64182 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64182?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64182, 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-64182

Explore →

Is Your Infrastructure Affected by CVE-2026-64182?

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