CVE-2024-36026: drm/amd/pm: fixes a random hang in S4 for SMU v13.0.4/11
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/pm: fixes a random hang in S4 for SMU v13.0.4/11
While doing multiple S4 stress tests, GC/RLC/PMFW get into
an invalid state resulting into hard hangs.
Adding a GFX reset as workaround just before sending the
MP1_UNLOAD message avoids this failure.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can cause some AMD GPU power-management systems to hard hang during S4 hibernate/resume stress conditions. The business impact is availability: affected workstations or devices may freeze and require recovery. The supplied sources do not show data exposure, privilege escalation, or active exploitation.
Executive priority
Treat as an operational stability issue, not an emergency security incident based on current evidence. Patch through normal kernel maintenance, prioritizing fleets where hibernate-related hangs affect productivity, kiosks, or managed endpoints.
Technical view
The resolved bug is in Linux drm/amd/pm for SMU v13.0.4/11. During repeated S4 testing, GC, RLC, and PMFW can enter an invalid state, causing hard hangs. Kernel stable commits add a GFX reset before sending MP1_UNLOAD as a workaround.
Likely exposure
Exposure appears limited to Linux systems using affected AMD GPU power-management paths, especially where S4 hibernate is used. The bundle identifies Linux kernel versions and stable branches but does not provide distro-specific package status, so backport validation is required.
Exploitation context
No active exploitation is supported by the supplied evidence. The CVE is not listed as KEV in the bundle, and the description frames the issue as a reliability failure found during S4 stress testing, not a remote attack path.
Researcher notes
Evidence is sparse and kernel-focused. The supplied record lacks CVSS, CWE, exploitability detail, and distro advisories. Avoid over-scoping: the described condition is AMD PM on SMU v13.0.4/11 during S4 flows, with a GFX reset workaround in stable commits.
Mitigation direction
Update to a kernel containing the referenced stable fixes.
Check Linux distribution advisories for backported fixes.
Prioritize affected AMD systems that use S4 hibernate.
Temporarily avoid S4 hibernate on impacted systems if patching is delayed.
Validation and detection
Inventory Linux systems with AMD GPU power-management hardware paths.
Confirm whether the running kernel includes the stable fix commit.
Check distro kernel changelogs for CVE-2024-36026 backports.
Review device history for hard hangs around S4 hibernate or resume.
Regression-test S4 behavior on patched representative hardware.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-36026 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.