CVE-2026-64152

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.8EG
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.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

iommu: Handle unmap error when iommu_debug is enabled

Sashiko noticed a latent bug where the map error flow called iommu_unmap() which calls iommu_debug_unmap_begin()/iommu_debug_unmap_end() however since this is an error path the map flow never actually established the original iommu_debug_map() it will malfunction.

Lift the unmap error handling into iommu_map_nosync() and reorder it so the trace_map()/iommu_debug_map() records the partial mapping and then immediately unmaps it. This avoid creating the unbalanced tracking and provides saner tracing instead of a unmap unmatched to any map.

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

Published

July 19, 2026

Last Modified

August 17, 2026

Advisory Details (2)

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

iommu: Handle unmap error when iommu_debug is enabled - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0cd028806efc148a75d4acf711d21db335a89661
generic

iommu: Handle unmap error when iommu_debug is enabled - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0735c54804c709d1b292f3b6947cfb560b2ce552

Vendor Advisories for CVE-2026-64152(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 / 157× 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 200 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64152?
CVE-2026-64152 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: iommu: Handle unmap error when iommu_debug is enabled Sashiko noticed a latent bug where the map error flow called iommu_unmap() which calls iommudebugunmapbegin()/iommudebugunmapend() however since this is an error path the map…
When was CVE-2026-64152 disclosed?
CVE-2026-64152 was first published in the National Vulnerability Database on July 19, 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-64152 actively exploited?
CVE-2026-64152 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.7% of all scored CVEs.
What is the CVSS score of CVE-2026-64152?
CVE-2026-64152 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64152?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64152, 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-64152

Explore →

Is Your Infrastructure Affected by CVE-2026-64152?

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

Start Free Scan →Browse All CVEs