Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 15 days later

    Published

  3. · 4 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-53053, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
NVDNVD · Modified3.1High8.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.

Affected products

  • Linux · Linux

    • affected 3332364e4ebc0581d133a334645a20fd13b580f1 – < 880a2e6c887c8f51870c0a00dfba3c8519178b65
    • affected 3332364e4ebc0581d133a334645a20fd13b580f1 – < 166a08644aa509e5d27e154d7fa774f4181df9e0
    • affected 3332364e4ebc0581d133a334645a20fd13b580f1 – < dbd76a537d8cb814e7f5b795ab21ecb7949c821d
    • affected 3332364e4ebc0581d133a334645a20fd13b580f1 – < 20b3c566e2702e5d4d0545be8a97029a2eebcc0e
    • affected 3332364e4ebc0581d133a334645a20fd13b580f1 – < dae251ff11d2d2208a029f98923756831cefec46
    • affected 3332364e4ebc0581d133a334645a20fd13b580f1 – < faad224fe0f0857a04ff2eb3c90f0de57f47d0f3
    • affected 1f03a258f20f1699ede29bb40804074db9398a0d
    • affected 5.4.17 – < 5.5
  • Linux · Linux

    • affected 5.5
    • unaffected < 5.5
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.91 – ≤ 6.12.*
    • unaffected 6.18.33 – ≤ 6.18.*
    • unaffected 7.0.10 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-53053 badge
[![CVE-2026-53053](https://cveledger.app/badge/CVE-2026-53053.svg)](https://cveledger.app/cve/CVE-2026-53053)

Record last updated .