# CVE-2026-53053: iommu/amd: Fix clone_alias() to use the original device's devid

> Incorrect device ID handling in AMD IOMMU alias cloning may propagate stale or wrong DMA translation entries, potentially allowing unauthorized memory access.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Jun 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-90416, BELL-CVE-2026-53053, DEBIAN-CVE-2026-53053, GHSA-8m6r-f5m5-x7p9, ROOT-OS-DEBIAN-11-CVE-2026-53053, ROOT-OS-DEBIAN-12-CVE-2026-53053, ROOT-OS-UBUNTU-2204-CVE-2026-53053, ROOT-OS-UBUNTU-2404-CVE-2026-53053, UBUNTU-CVE-2026-53053

## What is CVE-2026-53053?

CVE-2026-53053 is a high-severity vulnerability in Linux kernel, published on 24 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-681 (Incorrect Conversion between Numeric Types)

## Which versions are affected by CVE-2026-53053?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-53053?

Apply the vendor's patch.

## Is CVE-2026-53053 being exploited?

There is no known exploitation of CVE-2026-53053 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53053 and fix it if it is affected.

What it is: CVE-2026-53053 is a high-severity vulnerability in Linux kernel, published on 24 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-53053 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53053/ (Markdown: https://insights.sbomify.com/CVE-2026-53053/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53053
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53053
- OSV: https://osv.dev/vulnerability/CVE-2026-53053

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53053/
Summaries are generated and may contain mistakes; the official description above is the record.