All vulnerabilities

Servers and applications

CVE-2026-53164

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

Severity
Unrated
Published
25 Jun 2026
Last changed
6 Nov 2026
Added to UpHeron
6 Nov 2026
Fixed in
6.18.36, 7.0.13
Exploit chance
0.2% in the next 30 daysHigher than 5% of CVEs. EPSS by FIRST, 19 Nov 2026
Sources
CVE Program

Description

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

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.

From the CVE Program.

Affected software

SoftwareAffected versions
Linux kernelServers and applications · cna:linux|linux
  • From 6.16 before 6.18.36
  • From 6.19 before 7.0.13

About Linux kernel

Unix-like operating system kernel, basis for all Linux operating systems

From Wikidata, CC0 1.0.
GitHub stars
255,726GitHub, 15 Nov 2026
Forks
67,394GitHub, 15 Nov 2026
Developer
Linus TorvaldsWikidata
License
GNU General Public License, version 2.0Wikidata
Written in
CWikidata
First released
25 Aug 1991Wikidata
First published on GitHub
4 Sept 2011GitHub

References

  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-53164