CVE-2026-64072

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:

nvme: fix bio leak on mapping failure

The local bio is always NULL, so we'd leak the bio if the integrity mapping failed. Just get it directly from the request.

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

Published

July 19, 2026

Last Modified

September 3, 2026

Advisory Details (3)

Auto-updated Sep 3, 2026
No patch confirmed yet.
generic

nvme: fix bio leak on mapping failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvme: fix bio leak on mapping failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/51ec7fc4e10c5e332bf4007bdb7e4c6bf03c14c9
generic

nvme: fix bio leak on mapping failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2279cd9c61a330e5de4d6eb0bc422820dd6fdf36

Vendor Advisories for CVE-2026-64072(1)

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

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-18ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-18ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (141 versions)7.0.12-1—

Weakness Classification(1)

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

All Vendor Advisories

(6)

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 10× in last 7d / 50× 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 113 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-64072?
CVE-2026-64072 is a medium vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: nvme: fix bio leak on mapping failure The local bio is always NULL, so we'd leak the bio if the integrity mapping failed. Just get it directly from the request.
When was CVE-2026-64072 disclosed?
CVE-2026-64072 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on September 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64072 actively exploited?
CVE-2026-64072 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 97.3% of all scored CVEs.
What is the CVSS score of CVE-2026-64072?
CVE-2026-64072 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64072?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64072, 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-64072

Explore →

Is Your Infrastructure Affected by CVE-2026-64072?

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

Start Free Scan →Browse All CVEs