CVE-2026-53164

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-25. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

iommu/dma: Do not try to iommu_map a 0 length region in swiotlb

iommu_dma_iova_link_swiotlb() processes a mapping that is unaligned in three parts, the head, middle and trailer. If the middle is empty because there are no aligned pages it will call down to iommu_map() with a 0 size which the iommupt implementation will fail as illegal.

It then tries to do an error unwind and starts from the wrong spot corrupting the mapping so the eventual destruction triggers a WARN_ON.

Check for 0 length and avoid mapping and use offset not 0 as the starting point to unlink.

This is frequently triggered by using some kinds of thunderbolt NVMe drives that trigger forced SWIOTLB for unaligned memory. NVMe seems to pass in oddly aligned buffers for the passthrough commands from smartctl that hit this condition.

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

Published

June 25, 2026

Last Modified

July 7, 2026

Advisory Details (3)

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

iommu/dma: Do not try to iommu_map a 0 length region in swiotlb - kernel/git/stable/linux.git - Linux kernel stable tree

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

iommu/dma: Do not try to iommu_map a 0 length region in swiotlb - kernel/git/stable/linux.git - Linux kernel stable tree

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

iommu/dma: Do not try to iommu_map a 0 length region in swiotlb - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6ec91df8aff77e2e8fe3179c1f3fc15b43a40ba3

Vendor Advisories for CVE-2026-53164(1)

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

Affected Packages

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

Data Freshness Timeline

(refreshed 5× in last 7d / 46× 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 144 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53164?
CVE-2026-53164 is a medium vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: iommu/dma: Do not try to iommu_map a 0 length region in swiotlb iommudmaiovalinkswiotlb() processes a mapping that is unaligned in three parts, the head, middle and trailer. If the middle is empty because there are no aligned pages…
When was CVE-2026-53164 disclosed?
CVE-2026-53164 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53164 actively exploited?
CVE-2026-53164 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 94.5% of all scored CVEs.
What is the CVSS score of CVE-2026-53164?
CVE-2026-53164 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53164?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53164, 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-53164

Explore →

Is Your Infrastructure Affected by CVE-2026-53164?

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

Start Free Scan →Browse All CVEs