Review reviewHigh

CVE-2026-53053

Linux Linux, linux kernel

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

CVSS
8.8
EPSS
0.13%
2.91% percentile
CISA KEV
Not listed
Published
2026.06.25
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.13%
Technical severityCVSS 8.8

Vulnerability overview

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

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 3332364e4ebc0581d133a334645a20fd13b580f1 < dbd76a537d8cb814e7f5b795ab21ecb7949c821d, >= 3332364e4ebc0581d133a334645a20fd13b580f1 < 20b3c566e2702e5d4d0545be8a97029a2eebcc0e, >= 3332364e4ebc0581d133a334645a20fd13b580f1 < dae251ff11d2d2208a029f98923756831cefec46, >= 3332364e4ebc0581d133a334645a20fd13b580f1 < faad224fe0f0857a04ff2eb3c90f0de57f47d0f3, >= 1f03a258f20f1699ede29bb40804074db9398a0d, >= 5.4.17 < 5.5, >= 5.5, >= 5.4.17 < 6.12.91, >= 6.13 < 6.18.33, >= 6.19 < 7.0.10
Fixed versions
6.12.91, 6.18.33, 7.0.10

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CWE
Not available