Skip to main content

Linux Kernel CVE-2026-53053

| EUVDEUVD-2026-38921 HIGH
2026-06-24 Linux GHSA-8m6r-f5m5-x7p9
Linux Amd Information Disclosure Red Hat Suse
8.8
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
8.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
vuln.today AI
7.7 HIGH

Local low-priv access (AV:L/PR:L); AC:H because it needs a specific AMD IOMMU aliasing topology; S:C and C/I:H reflect cross-device DMA isolation loss, A:L as availability impact is secondary.

3.1 AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L
4.0 AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L
SUSE
7.0 HIGH
AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Red Hat
7.0 MEDIUM
qualitative

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Jun 28, 2026 - 08:59 vuln.today
CVSS changed
Jun 28, 2026 - 08:22 NVD
8.8 (HIGH)
Patch available
Jun 24, 2026 - 18:02 EUVD
CVE Published
Jun 24, 2026 - 16:29 cve.org
UNKNOWN (no severity yet)
CVE Published
Jun 24, 2026 - 16:29 cve.org
HIGH 8.8

DescriptionCVE.org

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.

AnalysisAI

Improper DMA-alias handling in the Linux kernel's AMD IOMMU driver lets a stale or incorrect Device Table Entry (DTE) be propagated to an alias PCI device, weakening the DMA isolation the IOMMU is meant to enforce. The flaw affects systems on AMD platforms where pci_for_each_dma_alias() supplies an alias-rather than the original-device to clone_alias(), causing the wrong source devid to be used when copying the DTE. EPSS is low (0.17%, 6th percentile) and there is no public exploit identified at time of analysis.

Technical ContextAI

The affected component is the AMD IOMMU (AMD-Vi) driver in the Linux kernel, which programs per-device Device Table Entries (DTEs) to govern DMA remapping and isolation. For devices that issue DMA under an aliased Requester ID (common with PCIe-to-PCI bridges and certain multifunction topologies), the kernel walks aliases via pci_for_each_dma_alias() and clones the DTE so the alias inherits the original device's translation/domain mapping. The bug is that clone_alias() assumed its first argument was always the original device, but the iterator passes either the original or an alias depending on topology; deriving the source devid from that argument therefore yields the wrong table index. The class of defect is incorrect resource/index identification leading to a stale or mismatched security-relevant mapping (CWE is listed as N/A by the source, but this aligns with use of incorrect/stale configuration data). The fix passes the original pdev as the opaque data argument to both the direct call and the iterator, and recomputes devid from it.

RemediationAI

Apply the stable kernel update that contains the fix for your branch: Vendor-released patch versions 6.12.91, 6.18.33, 7.0.10, or 7.1 (and equivalent distribution kernels carrying the backported commits). The fix corresponds to git.kernel.org stable commits dbd76a537d8cb814e7f5b795ab21ecb7949c821d, dae251ff11d2d2208a029f98923756831cefec46, 20b3c566e2702e5d4d0545be8a97029a2eebcc0e, and faad224fe0f0857a04ff2eb3c90f0de57f47d0f3 referenced from https://nvd.nist.gov/vuln/detail/CVE-2026-53053. Track your distribution's security advisory and install its corresponding kernel build, then reboot. As this is a kernel DMA-isolation correctness fix there is no clean userspace workaround; if patching must be deferred, compensating controls are limited to reducing exposure to untrusted DMA-capable devices-physically restrict access to PCIe/Thunderbolt/hot-plug slots and disable external DMA ports in firmware (trade-off: loss of those expansion/peripheral capabilities)-and avoid passing through or hot-plugging devices behind PCI bridges that trigger DMA aliasing in multi-tenant or VFIO scenarios (trade-off: constrains virtualization device-passthrough use).

More in Amd

View all
CVE-2021-22986 CRITICAL POC
9.8 Mar 31

On BIG-IP versions 16.0.x before 16.0.1.1, 15.1.x before 15.1.2.1, 14.1.x before 14.1.4, 13.1.x before 13.1.3.6, and 12.
CVE-2020-6103 CRITICAL POC
9.9 Jul 20

An exploitable code execution vulnerability exists in the Shader functionality of AMD Radeon DirectX 11 Driver atidxx64.
CVE-2020-6102 CRITICAL POC
9.9 Jul 20

An exploitable code execution vulnerability exists in the Shader functionality of AMD Radeon DirectX 11 Driver atidxx64.
CVE-2020-6101 CRITICAL POC
9.9 Jul 20

An exploitable code execution vulnerability exists in the Shader functionality of AMD Radeon DirectX 11 Driver atidxx64.
CVE-2020-6100 CRITICAL POC
9.9 Jul 20

An exploitable memory corruption vulnerability exists in AMD atidxx64.dll 26.20.15019.19000 graphics driver. Rated criti
CVE-2018-6546 CRITICAL POC
9.8 Apr 13

plays_service.exe in the plays.tv service before 1.27.7.0, as distributed in AMD driver-installation packages and Gaming
CVE-2021-3653 HIGH POC
8.8 Sep 29

A flaw was found in the KVM's AMD code for supporting SVM nested virtualization. Rated high severity (CVSS 8.8), this vu
CVE-2020-12138 HIGH POC
8.8 Apr 27

AMD ATI atillk64.sys 5.11.9.0 allows low-privileged users to interact directly with physical memory by calling one of se
CVE-2019-5098 HIGH POC
8.6 Dec 05

An exploitable out-of-bounds read vulnerability exists in AMD ATIDXX64.DLL driver, version 26.20.13001.29010. Rated high
CVE-2015-7724 HIGH POC
7.8 Jun 07

AMD fglrx-driver before 15.9 allows local users to gain privileges via a symlink attack. Rated high severity (CVSS 7.8),
CVE-2015-7723 HIGH POC
7.8 Jun 07

AMD fglrx-driver before 15.7 allows local users to gain privileges via a symlink attack. Rated high severity (CVSS 7.8),
CVE-2023-1048 HIGH POC
7.8 Feb 26

A vulnerability, which was classified as critical, has been found in TechPowerUp Ryzen DRAM Calculator 1.2.0.5.sys. Rate

Same technique Information Disclosure

View all
CVE-2019-2725 CRITICAL POC
9.8
CVE-2021-34523 CRITICAL POC
9.0
CVE-2013-2251 CRITICAL POC
9.8
CVE-2017-5638 CRITICAL POC
9.8
CVE-2025-24813 CRITICAL POC
9.8
CVE-2015-1701 HIGH POC
7.8
CVE-2017-0147 HIGH POC
7.5
CVE-2014-6324 HIGH POC
8.8

Vendor StatusVendor

SUSE

Severity: Important
Product Status
Container suse/sl-micro/6.0/base-os-container:2.1.3-7.168 Container suse/sl-micro/6.1/base-os-container:2.2.1-5.149 Affected
Container suse/sl-micro/6.0/rt-os-container:2.1.3-7.197 Container suse/sl-micro/6.1/rt-os-container:2.2.1-5.145 Affected
Container suse/sle-micro-rancher/5.3:latest Container suse/sle-micro-rancher/5.4:5.4.4.5.149 Affected
Container suse/sle-micro/base-5.5:2.0.4-5.8.296 Affected
Container suse/sle-micro/kvm-5.5:2.0.4-3.5.570 Affected

Share

CVE-2026-53053 vulnerability details – vuln.today
Back

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy