CVE-2026-53164

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

No CVSS.

References

Link	Resource
https://git.kernel.org/stable/c/6ec91df8aff77e2e8fe3179c1f3fc15b43a40ba3
https://git.kernel.org/stable/c/ab61c990a87d084f5565ee70340543e3a5394697
https://git.kernel.org/stable/c/b16f8d40bac9ced838d24c9842707af9ecae92e2

Configurations

No configuration.

History

25 Jun 2026, 09:16

Type	Values Removed	Values Added
New CVE

Information

Published : 2026-06-25 09:16

Updated : 2026-06-30 14:44

NVD link : CVE-2026-53164

Mitre link : CVE-2026-53164

CVE.ORG link : CVE-2026-53164

JSON object : View

Products Affected

No product.

CWE

No CWE.

{"id": "CVE-2026-53164", "cveTags": [], "metrics": {}, "affected": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "affectedData": [{"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "433a76207dcf5facc0183acb790f6e8398585258", "lessThan": "ab61c990a87d084f5565ee70340543e3a5394697", "versionType": "git"}, {"status": "affected", "version": "433a76207dcf5facc0183acb790f6e8398585258", "lessThan": "b16f8d40bac9ced838d24c9842707af9ecae92e2", "versionType": "git"}, {"status": "affected", "version": "433a76207dcf5facc0183acb790f6e8398585258", "lessThan": "6ec91df8aff77e2e8fe3179c1f3fc15b43a40ba3", "versionType": "git"}], "programFiles": ["drivers/iommu/dma-iommu.c"], "defaultStatus": "unaffected"}, {"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "6.16"}, {"status": "unaffected", "version": "0", "lessThan": "6.16", "versionType": "semver"}, {"status": "unaffected", "version": "6.18.36", "versionType": "semver", "lessThanOrEqual": "6.18.*"}, {"status": "unaffected", "version": "7.0.13", "versionType": "semver", "lessThanOrEqual": "7.0.*"}, {"status": "unaffected", "version": "7.1", "versionType": "original_commit_for_fix", "lessThanOrEqual": "*"}], "programFiles": ["drivers/iommu/dma-iommu.c"], "defaultStatus": "affected"}]}], "published": "2026-06-25T09:16:33.800", "references": [{"url": "https://git.kernel.org/stable/c/6ec91df8aff77e2e8fe3179c1f3fc15b43a40ba3", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/ab61c990a87d084f5565ee70340543e3a5394697", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/b16f8d40bac9ced838d24c9842707af9ecae92e2", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "vulnStatus": "Awaiting Analysis", "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\niommu/dma: Do not try to iommu_map a 0 length region in swiotlb\n\niommu_dma_iova_link_swiotlb() processes a mapping that is unaligned in three\nparts, the head, middle and trailer. If the middle is empty because there\nare no aligned pages it will call down to iommu_map() with a 0 size\nwhich the iommupt implementation will fail as illegal.\n\nIt then tries to do an error unwind and starts from the wrong spot\ncorrupting the mapping so the eventual destruction triggers a WARN_ON.\n\nCheck for 0 length and avoid mapping and use offset not 0 as the starting\npoint to unlink.\n\nThis is frequently triggered by using some kinds of thunderbolt NVMe\ndrives that trigger forced SWIOTLB for unaligned memory. NVMe seems to\npass in oddly aligned buffers for the passthrough commands from smartctl\nthat hit this condition."}], "lastModified": "2026-06-30T14:44:27.313", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}