CVE-2021-47362

drm/amd/pm: Update intermediate power state for SI

MEDIUM
5.5
CVSS Score
Published: May 21, 2024 at 03:03 PM UTC
Updated: June 17, 2026 at 04:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 4.14.74v ≥ 4.18.12v ≥ 4.9.131v < 5.10.704.14.74 ≤ v < 4.154.18.12 ≤ v < 4.194.19 ≤ v < 5.10.704.19 ≤ v < 5.14.94.19 ≤ v < 5.154.9.131 ≤ v < 4.105.11 ≤ v < 5.14.92ab4d0e74256fc49b7b270f63c1d1e47c2455abc2c83e77a3e35dc91350cea077d1aaefdc0a612974.14.744.18.124.9.13146cb720a8a3ece894eff4e1b85b3925efb71afd25.15 rc15.15 rc265c96da9c684946d0874bf911fdb50a3b497cb30
Vendor states this is fixed in 06a18e64256f7aecb5a27df02faa3568fcd3c105 (fixed)
Vendor states this is fixed in 68d4fbe6220cd1f3d07cab0a4901e62f8c12cc68 (fixed)
Vendor states this is fixed in ab39d3cef526ba09c4c6923b4cd7e6ec1c5d4faa (fixed)
Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.19 (unaffected)
Vendor states this is fixed in 5.10.70 (unaffected)
Vendor states this is fixed in 5.14.9 (unaffected)
Vendor states this is fixed in 5.15 (unaffected)

References (3)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/06a18e64256f7aecb5a27df02faa3568fcd3c105
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/68d4fbe6220cd1f3d07cab0a4901e62f8c12cc68
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/ab39d3cef526ba09c4c6923b4cd7e6ec1c5d4faa

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-476

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card