CVE-2026-64020

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. the CNA's CVSS baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

nvme-pci: fix dma_vecs leak on p2p memory

We don't unmap P2P memory, so we don't need to track it. The dma_vec allocation was getting leaked on the completion.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/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
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (2)

Auto-updated Jul 21, 2026
No patch confirmed yet.
generic

nvme-pci: fix dma_vecs leak on p2p memory - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/85686c72966c5ee637893f124ddb31a1cace7bee
generic

nvme-pci: fix dma_vecs leak on p2p memory - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/24ea0de233d9ebb5ebd6f6018eaf2084af25e3dd

Vendor Advisories for CVE-2026-64020(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)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu

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

(1 across 1 ecosystem)
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)

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 29× in last 7d / 156× 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 204 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64020?
CVE-2026-64020 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix dma_vecs leak on p2p memory We don't unmap P2P memory, so we don't need to track it. The dma_vec allocation was getting leaked on the completion.
When was CVE-2026-64020 disclosed?
CVE-2026-64020 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64020 actively exploited?
CVE-2026-64020 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 73.0% of all scored CVEs.
What is the CVSS score of CVE-2026-64020?
CVE-2026-64020 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-64020?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64020, 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-64020

Explore →

Is Your Infrastructure Affected by CVE-2026-64020?

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

Start Free Scan →Browse All CVEs