Menu

Star on GitHub · 3.2k

CVE-2026-53053

8.8 · HIGH

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…

Published Jun 24, 2026EPSS 0.13%

Overview

CVE-2026-53053 is a high-severity vulnerability. It was published on June 24, 2026 and has a CVSS 3.1 base score of 8.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 8.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

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

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-53053?

CVE-2026-53053 is a high-severity vulnerability. It was published on June 24, 2026 and has a CVSS 3.1 base score of 8.8 (HIGH).

How severe is CVE-2026-53053?

This vulnerability has a CVSS 3.1 base score of 8.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-53053?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-53053?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-53053 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all