dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53053

HIGH · 8.8 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 6.12.91 / 6.18.33 or later.
See remediation →
90/100
Remediation priority · Urgent
Zero-click Patch available 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The clone_alias() function in the AMD IOMMU driver incorrectly assumes the first argument is always the original device pointer. However, pci_for_each_dma_alias() may pass either the original or alias device based on topology. This causes incorrect devid lookup when copying Device Table Entries (DTE), leading to wrong or stale DTE entries being propagated to alias devices. This can result in improper DMA routing, potentially causing data corruption or unauthorized memory access.

MitigationThis is a kernel-level logic bug requiring a code fix. The patch modifies clone_alias() to receive the original device as opaque data and compute the devid from it, ensuring correct DTE propagation. No practical workaround exists other than applying the kernel update.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 5.4.17, < 6.12.91>= 6.13, < 6.18.33>= 6.19, < 7.0.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify AMD IOMMU is enabled
    Check kernel command line in /proc/cmdline for 'amd_iommu=' parameter, or check if the amd_iommu module is loaded via 'lsmod | grep amd_iommu', or check /sys/kernel/iommu/amd/ directory exists
    Affected if AMD IOMMU is enabled or loaded in the kernel
  2. Identify the kernel version
    Run 'uname -r' to get the running kernel version, then compare against known patched kernel versions for this CVE
    Affected if The running kernel version is older than the version that includes the fix for this vulnerability
  3. Locate the AMD IOMMU driver source
    Check for /drivers/iommu/amd_iommu.c in the kernel source or module directory, or locate via 'modinfo amd_iommu'
    Affected if The amd_iommu driver is present in the system
  4. Inspect the clone_alias function for the vulnerability
    Examine the clone_alias() function implementation in the AMD IOMMU driver source code; look for whether it correctly retrieves the original device from the opaque data pointer rather than assuming the first argument is always the original device
    Affected if The clone_alias() function uses the first argument directly as the original device without checking if it was passed as an alias from pci_for_each_dma_alias()
  5. Check for PCI devices using DMA aliases
    Review PCI topology via 'lspci' and check if any devices have DMA aliases configured, particularly in multi-function or bridge topologies that would trigger pci_for_each_dma_alias()
    Affected if The system has PCI devices where pci_for_each_dma_alias() may pass alias devices instead of the original device to the callback

The system is affected if AMD IOMMU is enabled and the kernel version is older than the patched version, AND the clone_alias() function implementation does not correctly handle the case where pci_for_each_dma_alias() passes an alias device instead of the original device.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 6.12.91 / 6.18.33 / 7.0.10 or later
Fixed in 6.12.916.18.337.0.10
Vendor patch git.kernel.org →
Interim mitigation

This is a kernel-level logic bug requiring a code fix. The patch modifies clone_alias() to receive the original device as opaque data and compute the devid from it, ensuring correct DTE propagation. No practical workaround exists other than applying the kernel update.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53053 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53053 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data