CVE-2026-53164

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

Published Jun 25, 2026 CVSS 3.1 · 5.5 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The kernel fails to guard against zero‑length regions when mapping with SWIOTLB, causing the iommupt implementation to reject the request and triggering an error unwind that corrupts internal mapping state. This omission leads to a WARN_ON during cleanup, indicating a kernel consistency violation that could result in a system crash or unpredictable behavior. The flaw is documented as CWE‑805, with the NVD mapping also noting NVD‑CWE‑noinfo, and manifests when unaligned buffers are passed from thunderbolt NVMe devices, particularly through smartctl passthrough commands.

Affected Systems

The vulnerability affects the Linux kernel, as identified by the vendor listing of Linux:Linux. No specific kernel version range is supplied in the data, so all kernels potentially containing the unpatched routine are considered susceptible until patch information is applied.

Risk and Exploitability

Because the flaw is triggered by a specific hardware interaction that forces SWIOTLB usage with oddly aligned buffers, an attacker would need to cause such a condition on the target system. The CVSS score of 5.5 indicates moderate risk, while the EPSS score of < 1% shows a very low probability of exploitation. The issue is not listed in CISA KEV, so there is currently no evidence of active exploitation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the Linux kernel to a version that includes the fix for the zero‑length region mapping error.
  • If an update is unavailable, avoid using thunderbolt NVMe drives with smartctl or similar utilities that push unaligned buffers through SWIOTLB.
  • Continuously monitor system logs for WARN_ON messages related to iommu_dma and SWIOTLB to detect potential exploitation attempts.

Generated by OpenCVE AI on August 12, 2026 at 07:49 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8726-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8727-1 Linux kernel (OEM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-1 Linux kernel (GCP) vulnerabilities
Ubuntu USN Ubuntu USN USN-8760-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-8726-2 Linux kernel (Raspberry Pi) vulnerabilities
Ubuntu USN Ubuntu USN USN-8726-3 Linux kernel (IBM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8800-1 Linux kernel (NVIDIA BaseOS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8760-2 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-8726-4 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-2 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-3 Linux kernel (Oracle) vulnerabilities
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-665
Type Values Removed Values Added
Weaknesses CWE-805
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate

Type Values Removed Values Added
Weaknesses CWE-665
Type Values Removed Values Added
Description 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.
Title iommu/dma: Do not try to iommu_map a 0 length region in swiotlb
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Nov 6, 2026, 4:24 PM
Reserved
Jun 9, 2026, 7:44 AM
Status
Analyzed
Published
Jun 25, 2026, 9:16 AM
Modified
Nov 6, 2026, 5:18 PM
Severity
Moderate
Public date
Jun 25, 2026, 12:00 AM