Security readout for executives and security teams
Plain-English summary
CVE-2024-36024 is a Linux kernel AMD display bug that can cause a hardware hang during a display controller power-state handshake. The public record describes a stability failure, not data theft or remote code execution.
Executive priority
Treat as a reliability and availability issue until vendor guidance says otherwise. Prioritize patching affected AMD display fleets, but do not escalate as confirmed exploited or remote compromise based on the provided evidence.
Technical view
The resolved kernel change disables idle reallow during command/gpint execution to avoid a DMCUB race while entering IPS1. Missing the IPS2 transition can lead to touching INBOX1 RPTR and a hardware hang in drm/amd/display.
Likely exposure
Exposure appears limited to Linux systems using affected kernel builds with the AMD display driver path. The provided affected-version data is sparse and should be mapped through each distribution or kernel vendor.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not marked KEV. The described impact is a hardware hang caused by a race condition, with no exploit mechanism or attacker prerequisites documented.
Researcher notes
Evidence supports a kernel drm/amd/display race leading to hardware hang. CVSS, CWE, attacker requirements, and distro-specific affected ranges are not supplied. Avoid assuming exploitability beyond the documented hang condition.
Mitigation direction
- Apply a kernel update containing the referenced stable fixes.
- Check distribution advisories for backported fixes and affected package versions.
- Prioritize workstations, laptops, and hosts using AMD display hardware.
- Monitor vendor guidance if no patched package is available yet.
Validation and detection
- Inventory Linux kernel versions across AMD display systems.
- Confirm whether vendor kernels include the referenced stable commits.
- Review vendor security advisories for exact fixed package versions.
- Track recurring AMD display or GPU hardware hang reports.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2024-36024 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/2aac387445610d6dfd681f5214388e86f5677ef7CVE reference, Linux
- https://git.kernel.org/stable/c/6226a5aa77370329e01ee8abe50a95e60618ce97CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.