CVE-2026-53053

iommu/amd: Fix clone_alias() to use the original device's devid

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

iommu/amd: Fix clone_alias() to use the original device's devid

Currently clone_alias() assumes first argument (pdev) is always the
original device pointer. This function is called by
pci_for_each_dma_alias() which based on topology decides to send
original or alias device details in first argument.

This meant that the source devid used to look up and copy the DTE
may be incorrect, leading to wrong or stale DTE entries being
propagated to alias device.

Fix this by passing the original pdev as the opaque data argument to
both the direct clone_alias() call and pci_for_each_dma_alias(). Inside
clone_alias(), retrieve the original device from data and compute devid
from it.

Analysis

AI-generated

Technical impact

The vulnerability comes from the iommu/amd clone_alias() function incorrectly assuming that its first argument is always the original device pointer. Because pci_for_each_dma_alias() can provide an alias device pointer, the source device identifier used to look up and copy the Device Table Entry (DTE) may be wrong. This misinterpretation can be classified as a CWE-681: Incorrect Function Parameter usage and also involves a conflict between security policies (CWE-694). The result is that wrong or stale DTE entries are propagated to the alias device.

Affected Systems

Any Linux kernel that uses the iommu/amd module prior to the commit that fixes clone_alias() is potentially affected. The affected versions are not explicitly enumerated in the CVE description, so any system running a kernel built before the patch is considered vulnerable. The vendor is the Linux kernel project.

Risk and Exploitability

The CVSS score of 8.8 indicates a high severity. The EPSS score is < 1% and the vulnerability is not listed in CISA KEV. The description does not state an explicit attack vector. Based on the description, it is inferred that a local attacker with the ability to load a malicious kernel module or influence PCI device enumeration could trigger the incorrect mapping, resulting in stale or incorrect DTE propagation. Consequently, the risk remains high, especially in environments that rely on strict device isolation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a version that contains the commit which fixes clone_alias() to correctly use the original device’s devid.
  • Apply the kernel upgrade to all hosts that utilize the AMD IOMMU subsystem, including servers, workstations, and virtual machine guests.
  • After upgrading, monitor kernel logs for iommu or PCI‑related warnings and verify that alias device mappings reflect the correct device identifiers.

Generated by OpenCVE AI on October 19, 2026 at 23:36 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4906-1 linux security update
Ubuntu USN Ubuntu USN USN-8566-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8568-1 Linux kernel (OEM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8569-1 Linux kernel (HWE) vulnerabilities
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-8781-1 Linux kernel (NVIDIA Tegra) 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': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-681
Type Values Removed Values Added
Weaknesses CWE-347
CWE-704
Type Values Removed Values Added
Metrics cvssV3_1

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

cvssV3_1

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

Type Values Removed Values Added
Weaknesses CWE-694
References
Metrics threat_severity

None

cvssV3_1

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

threat_severity

Moderate

Type Values Removed Values Added
Weaknesses CWE-347
CWE-704
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Fix clone_alias() to use the original device's devid Currently clone_alias() assumes first argument (pdev) is always the original device pointer. This function is called by pci_for_each_dma_alias() which based on topology decides to send original or alias device details in first argument. This meant that the source devid used to look up and copy the DTE may be incorrect, leading to wrong or stale DTE entries being propagated to alias device. Fix this by passing the original pdev as the opaque data argument to both the direct clone_alias() call and pci_for_each_dma_alias(). Inside clone_alias(), retrieve the original device from data and compute devid from it.
Title iommu/amd: Fix clone_alias() to use the original device's devid
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
Oct 30, 2026, 12:26 PM
Reserved
Jun 9, 2026, 7:44 AM
Status
Modified
Published
Jun 24, 2026, 5:17 PM
Modified
Oct 30, 2026, 1:19 PM
Severity
Moderate
Public date
Jun 24, 2026, 12:00 AM