CVE-2026-64153

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

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

drm/msm: Fix iommu_map_sgtable() return value check and avoid WARN

Commit "iommu: return full error code from iommu_map_sg[_atomic]()" changed iommu_map_sgtable() to return an ssize_t and negative values in error cases, rather than a size_t and a zero.

Store the return value in the appropriate type and in case of error, return it rather than WARNing.

Patchwork: https://patchwork.freedesktop.org/patch/719685/

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

Published

July 19, 2026

Last Modified

August 17, 2026

Advisory Details (7)

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

drm/msm: Fix iommu_map_sgtable() return value check and avoid WARN - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/msm: Fix iommu_map_sgtable() return value check and avoid WARN - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7256e54583aee21e23929e7554278c2f5c1a08b1
generic

drm/msm: Fix iommu_map_sgtable() return value check and avoid WARN - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/55e0f0d1c1a4ee1e46da7da4d443eb3044fb3851
generic

drm/msm: Fix iommu_map_sgtable() return value check and avoid WARN - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3e3c3c95ef4fe17231a9149e27bcfc9dae2dd89f
generic

drm/msm: Fix iommu_map_sgtable() return value check and avoid WARN - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3c2cdb7c07f664b77e2a75b50793b845d5742efa
generic

drm/msm: Fix iommu_map_sgtable() return value check and avoid WARN - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3a45af37733446e114bf19b0209fe7d8089bdb8b
generic

drm/msm: Fix iommu_map_sgtable() return value check and avoid WARN - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3457807aeb88077712f0a7cb65c3ca5120773d75

Vendor Advisories for CVE-2026-64153(1)

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

Patch Availability(16)

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
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

(16)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-64153?
CVE-2026-64153 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/msm: Fix iommumapsgtable() return value check and avoid WARN Commit "iommu: return full error code from iommumapsg_atomic" changed iommumapsgtable() to return an ssize_t and negative values in error cases, rather than a size_t…
When was CVE-2026-64153 disclosed?
CVE-2026-64153 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-64153 actively exploited?
CVE-2026-64153 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 96.5% of all scored CVEs.
What is the CVSS score of CVE-2026-64153?
CVE-2026-64153 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-64153?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64153, 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-64153

Explore →

Is Your Infrastructure Affected by CVE-2026-64153?

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