CVE-2026-53053
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 8.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-681
- Record status
- Modified
Affected
- Linux Kernel < 6.12.91
- Linux Kernel < 6.18.33
- Linux Kernel < 7.0.10
Attack profile CVSS 3.1 · 8.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-53053.md and follow it. Check whether this project is affected by CVE-2026-53053. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/20b3c566e2702e5d4d0545be8a97029a2eebcc0e
- https://git.kernel.org/stable/c/dae251ff11d2d2208a029f98923756831cefec46
- https://git.kernel.org/stable/c/dbd76a537d8cb814e7f5b795ab21ecb7949c821d
- https://git.kernel.org/stable/c/faad224fe0f0857a04ff2eb3c90f0de57f47d0f3
References
- https://git.kernel.org/stable/c/166a08644aa509e5d27e154d7fa774f4181df9e0
- https://git.kernel.org/stable/c/20b3c566e2702e5d4d0545be8a97029a2eebcc0e
- https://git.kernel.org/stable/c/880a2e6c887c8f51870c0a00dfba3c8519178b65
- https://git.kernel.org/stable/c/dae251ff11d2d2208a029f98923756831cefec46
- https://git.kernel.org/stable/c/dbd76a537d8cb814e7f5b795ab21ecb7949c821d
- https://git.kernel.org/stable/c/faad224fe0f0857a04ff2eb3c90f0de57f47d0f3