CVE-2026-64152

iommu: Handle unmap error when iommu_debug is enabled

Published Jul 19, 2026 CVSS 3.1 · 7.8 High EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

iommu: Handle unmap error when iommu_debug is enabled

Sashiko noticed a latent bug where the map error flow called iommu_unmap()
which calls iommu_debug_unmap_begin()/iommu_debug_unmap_end() however
since this is an error path the map flow never actually established the
original iommu_debug_map() it will malfunction.

Lift the unmap error handling into iommu_map_nosync() and reorder it so
the trace_map()/iommu_debug_map() records the partial mapping and then
immediately unmaps it. This avoid creating the unbalanced tracking and
provides saner tracing instead of a unmap unmatched to any map.

Analysis

AI-generated

Technical impact

A bug in the Linux kernel's IOMMU subsystem causes unbalanced handling of an unmap error when the debug mode is active. On the error path, iommu_unmap() invokes trace functions that expect a prior map entry, but because the map was never established this leads to unmatched tracing and faulty resource bookkeeping. The flaw falls under CWE-832: Improper Resource Management and can corrupt kernel state or trigger a kernel panic, resulting in a denial of service for the affected system.

Affected Systems

All Linux kernel releases that contain the IOMMU debug path are potentially affected, as the issue resides in the core iommu code without documented version constraints. The kernel versions indicated by the CPE entries, including generic and release candidates such as 7.1 rc1-rc3, are part of the affected set. The vulnerability is present in any kernel configured with iommu_debug enabled.

Risk and Exploitability

The CVSS score of 7.8 indicates a high severity vulnerability, while the EPSS score of less than 1% shows low likelihood of exploitation. The vulnerability is not listed in the CISA KEV catalog. The available information does not describe a remote attack vector; the needed conditions for exploitation, such as triggering an IOMMU map failure while debug mode is enabled or having the capability to modify kernel state, suggest that an attacker would need privileged access or the ability to influence kernel execution. These conditions are therefore inferred from the description rather than explicitly documented in the CVE record.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest Linux kernel update that includes the patch for CVE-2026-64152.
  • If the patch is not yet available, disable IOMMU debug tracing by turning off the 'iommu_debug' kernel configuration option or removing any 'iommu_debug' kernel boot parameters to avoid the faulty tracing path.
  • If IOMMU debug features are not required, consider disabling the entire IOMMU subsystem or limiting its use through device isolation or access controls until a fix is deployed.

Generated by OpenCVE AI on August 17, 2026 at 21:05 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8593-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8603-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8618-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8663-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-8664-1 Linux kernel (NVIDIA BaseOS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-1 Linux kernel (GCP) 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
Weaknesses NVD-CWE-noinfo
CPEs cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:*
Type Values Removed Values Added
Metrics 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'}

cvssV3_1

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

Type Values Removed Values Added
Weaknesses CWE-832
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

Low

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: iommu: Handle unmap error when iommu_debug is enabled Sashiko noticed a latent bug where the map error flow called iommu_unmap() which calls iommu_debug_unmap_begin()/iommu_debug_unmap_end() however since this is an error path the map flow never actually established the original iommu_debug_map() it will malfunction. Lift the unmap error handling into iommu_map_nosync() and reorder it so the trace_map()/iommu_debug_map() records the partial mapping and then immediately unmaps it. This avoid creating the unbalanced tracking and provides saner tracing instead of a unmap unmatched to any map.
Title iommu: Handle unmap error when iommu_debug is enabled
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
Aug 5, 2026, 12:39 PM
Reserved
Jul 19, 2026, 7:54 AM
Status
Analyzed
Published
Jul 19, 2026, 4:17 PM
Modified
Aug 17, 2026, 5:11 PM
Severity
Low
Public date
Jul 19, 2026, 12:00 AM