CVE-2026-64151

HIGHPre-NVD 8.48.4—
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

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

iommupt: Check for missing PAGE_SIZE in the pgsize_bitmap

Sashiko pointed out that the driver could drop PAGE_SIZE from the pgsize_bitmap. That is technically allowed but nothing does it, and such an iommu_domain would not be used with the DMA API today.

Still, it is against the design and it is trivial to fix up. Lift the PT_WARN_ON to the if branch and just skip the fast path.

CVSS v3
8.4
EG Score
8.4(medium)
EG Risk
42(Track)
EG Risk 42/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
Severity84% × 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 17, 2026

Advisory Details (2)

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

iommupt: Check for missing PAGE_SIZE in the pgsize_bitmap - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8ef3f77c440005c7f04229a75976bfc078364247
generic

iommupt: Check for missing PAGE_SIZE in the pgsize_bitmap - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/00850f41da24423587abd6124a790dd4f12bcef3

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

Frequently asked(5)

What is CVE-2026-64151?
CVE-2026-64151 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: iommupt: Check for missing PAGESIZE in the pgsizebitmap Sashiko pointed out that the driver could drop PAGE_SIZE from the pgsize_bitmap. That is technically allowed but nothing does it, and such an iommu_domain would not be used…
When was CVE-2026-64151 disclosed?
CVE-2026-64151 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-64151 actively exploited?
CVE-2026-64151 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.0% of all scored CVEs.
What is the CVSS score of CVE-2026-64151?
CVE-2026-64151 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-64151?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64151, 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-64151

Explore →

Is Your Infrastructure Affected by CVE-2026-64151?

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

Start Free Scan →Browse All CVEs