Answer in brief
CVE-2026-53164 records a Medium severity (CVSS 5.5) vulnerability in iommu/dma: Do not try to iommu_map a 0 length region in swiotlb. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=433a76207dcf5facc0183acb790f6e8398585258 <ab61c990a87d084f5565ee70340543e3a5394697 || >=433a76207dcf5facc0183acb790f6e8398585258 <b16f8d40bac9ced838d24c9842707af9ecae92e2 || >=433a76207dcf5facc0183acb790f6e8398585258 <6ec91df8aff77e2e8fe3179c1f3fc15b43a40ba3 | ab61c990a87d084f5565ee70340543e3a5394697, b16f8d40bac9ced838d24c9842707af9ecae92e2, 6ec91df8aff77e2e8fe3179c1f3fc15b43a40ba3 |
| Linux/Linuxgeneric | 6.16 | Not reported |
Published upstream
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 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 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.
Quoted source text, attributed separately from HOL analysis.