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-23213

drm/amd/pm: Disable MMIO access during SMU Mode 1 reset

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amd/pm: Disable MMIO access during SMU Mode 1 reset During Mode 1 reset, the ASIC undergoes a reset cycle and becomes temporarily inaccessible via PCIe. Any attempt to access MMIO registers during this window (e.g., from interrupt handlers or other driver threads) can result in uncompleted PCIe transactions, leading to NMI panics or system hangs. To prevent this, set the `no_hw_access` flag to true immediately after triggering the reset. This signals other driver components to skip register accesses while the device is offline. A memory barrier `smp_mb()` is added to ensure the flag update is globally visible to all cores before the driver enters the sleep/wait state. (cherry picked from commit 7edb503fe4b6d67f47d8bb0dfafb8e699bb0f8a4)

Timeline

  1. ID reserved

    By Linux

  2. · 36 days later

    Published

  3. · 9 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-23213, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (11 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected ea8139d8d59bd6f014b317e7423345169a56fe49 – < 4027796f024dabb2766afde4f7e772c92bc4d056
    • affected ea8139d8d59bd6f014b317e7423345169a56fe49 – < b2b9ac2bb2c5b5b0a39f7f422bbe12d3ea4ccf34
    • affected ea8139d8d59bd6f014b317e7423345169a56fe49 – < c1853ebbec980d5c05d431bfd6ded73b1363fd00
    • affected ea8139d8d59bd6f014b317e7423345169a56fe49 – < cd7ff7fd3e4b77f0b5a292e0926532eaa07c5162
    • affected ea8139d8d59bd6f014b317e7423345169a56fe49 – < 0de604d0357d0d22cbf03af1077d174b641707b6
  • Linux · Linux

    • affected 5.9
    • unaffected < 5.9
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.70 – ≤ 6.12.*
    • unaffected 6.18.10 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .