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-2021-47362drm/amd/pm: Update intermediate power state for SI

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amd/pm: Update intermediate power state for SI Update the current state as boot state during dpm initialization. During the subsequent initialization, set_power_state gets called to transition to the final power state. set_power_state refers to values from the current state and without current state populated, it could result in NULL pointer dereference. For ex: on platforms where PCI speed change is supported through ACPI ATCS method, the link speed of current state needs to be queried before deciding on changing to final power state's link speed. The logic to query ATCS-support was broken on certain platforms. The issue became visible when broken ATCS-support logic got fixed with commit f9b7f3703ff9 ("drm/amdgpu/acpi: make ATPX/ATCS structures global (v2)"). Bug: https://gitlab.freedesktop.org/drm/amd/-/issues/1698

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 2 years 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-2021-47362, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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.24% · top 85% of all CVEs (16 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 2ab4d0e74256fc49b7b270f63c1d1e47c2455abc – < 68d4fbe6220cd1f3d07cab0a4901e62f8c12cc68
    • affected 2ab4d0e74256fc49b7b270f63c1d1e47c2455abc – < 06a18e64256f7aecb5a27df02faa3568fcd3c105
    • affected 2ab4d0e74256fc49b7b270f63c1d1e47c2455abc – < ab39d3cef526ba09c4c6923b4cd7e6ec1c5d4faa
    • affected 2c83e77a3e35dc91350cea077d1aaefdc0a61297
    • affected 46cb720a8a3ece894eff4e1b85b3925efb71afd2
    • affected 65c96da9c684946d0874bf911fdb50a3b497cb30
    • affected 4.9.131 – < 4.10
    • affected 4.14.74 – < 4.15
    • affected 4.18.12 – < 4.19
  • Linux · Linux

    • affected 4.19
    • unaffected < 4.19
    • unaffected 5.10.70 – ≤ 5.10.*
    • unaffected 5.14.9 – ≤ 5.14.*
    • unaffected 5.15 – ≤ *

References

References3

Sources

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

Badge for a README or a ticket

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

Record last updated .