Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-53053: iommu/amd: Fix clone_alias() to use the original device's devid

HighCVSS 8.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 35/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.13% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 166a08644aa509e5d27e154d7fa774f4181df9e0, 20b3c566e2702e5d4d0545be8a97029a2eebcc0e, 5.5; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 166a08644aa509e5d27e154d7fa774f4181df9e0, 20b3c566e2702e5d4d0545be8a97029a2eebcc0e, 5.5; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Jun 24, 2026
Updated
Oct 30, 2026
EPSS
0.1% · 2th percentile

Report tools

JSON

Action score

35

Monitor

Low priority for now.

CVSS
35 / 40 · 8.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
8.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-53053

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 1f03a258f20f1699ede29bb40804074db9398a0d, 5.5affected
    • 3332364e4ebc0581d133a334645a20fd13b580f1 and later · before 880a2e6c887c8f51870c0a00dfba3c8519178b65affected · git
    • 3332364e4ebc0581d133a334645a20fd13b580f1 and later · before 166a08644aa509e5d27e154d7fa774f4181df9e0affected · git
    • 3332364e4ebc0581d133a334645a20fd13b580f1 and later · before dbd76a537d8cb814e7f5b795ab21ecb7949c821daffected · git
    • 3332364e4ebc0581d133a334645a20fd13b580f1 and later · before 20b3c566e2702e5d4d0545be8a97029a2eebcc0eaffected · git
    • 3332364e4ebc0581d133a334645a20fd13b580f1 and later · before dae251ff11d2d2208a029f98923756831cefec46affected · git
    • 3332364e4ebc0581d133a334645a20fd13b580f1 and later · before faad224fe0f0857a04ff2eb3c90f0de57f47d0f3affected · git
    • 5.4.17 and later · before 5.5affected · semver
    • before 5.5not affected · semver
    • 6.1.191 and later · up to and including 6.1.*not affected · semver

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.4.17 and later · before 6.12.91
  • linux linux kernel6.13 and later · before 6.18.33
  • linux linux kernel6.19 and later · before 7.0.10

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-53050Jun 24, 2026 · quota: Fix race of dquot_scan_active() with quota deactivation
    31Monitor
  • ← EarlierCVE-2026-53051Jun 24, 2026 · PCI: tegra194: Fix CBB timeout caused by DBI access before core power-on
    22Monitor
  • Later →CVE-2026-53055Jun 24, 2026 · crypto: hisilicon/sec2 - prevent req used-after-free for sec
    39Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux166a08644aa509e5d27e154d7fa774f4181df9e0Vendor (CNA)
Linux Linux20b3c566e2702e5d4d0545be8a97029a2eebcc0eVendor (CNA)
Linux Linux5.5Vendor (CNA)
Linux Linux880a2e6c887c8f51870c0a00dfba3c8519178b65Vendor (CNA)
Linux Linuxdae251ff11d2d2208a029f98923756831cefec46Vendor (CNA)
Linux Linuxdbd76a537d8cb814e7f5b795ab21ecb7949c821dVendor (CNA)
Linux Linuxfaad224fe0f0857a04ff2eb3c90f0de57f47d0f3Vendor (CNA)
azl3 kernel 6.6.152.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
almalinux:kernel6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:linux6.1.192-1 · Debian:12Package registry (OSV)
debian:linux6.12.94-1 · Debian:13Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)

+7

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-6392625 days apartbpf: sockmap: fix tail fragment offset in bpf_msg_push_data
    33Monitor
  • CVE-2026-531331 days apartRDMA/umem: Fix truncation for block sizes >= 4G
    31Monitor
  • CVE-2026-9814393 days apartaccel: ethosu: Don't read the U65 rounding mode as a storage mode
    31Monitor
  • CVE-2026-9804993 days apartbpf: zero extend the result of an arena 32-bit cmpxchg
    22Monitor
  • CVE-2026-9809593 days apartaf_packet: Don't cast tpacket_hdr.tp_len to int in tpacket_parse_header().
    22Monitor

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records