CVE-2026-64072

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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, GitHub Security Advisory, NVD CVSS v3
5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

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.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

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 (value × EchelonGraph’s weight)
Severity55% × 45%
The EG Score, 5.5 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 19, 2026

Last Modified

September 3, 2026

Advisory Details (3)

Auto-updated Sep 3, 2026
Patch available.
Web page

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

https://git.kernel.org/stable/c/fea4b46f84c50caf93c6c0f2a54b1be2edfb4491
Web page

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

https://git.kernel.org/stable/c/51ec7fc4e10c5e332bf4007bdb7e4c6bf03c14c9
Web page

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(8)

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 rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (142 versions)
  • every version up to 7.0.12-1: fixed in 7.0.12-1
—

Weakness Classification(1)

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

All Vendor Advisories

(8)

Data Freshness Timeline

(refreshed 11× in last 7d / 43× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 146 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 46 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-64072?
CVE-2026-64072 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-64072 published?
The CVE record for CVE-2026-64072 was published on July 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 3, 2026; the record at its source may have been updated since.
Is CVE-2026-64072 actively exploited?
CVE-2026-64072 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-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?
A fix for CVE-2026-64072 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-64072 are linked in the Vendor Advisories panel on this page.

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.