CVE-2024-35799: drm/amd/display: Prevent crash when disable stream
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Prevent crash when disable stream
[Why]
Disabling stream encoder invokes a function that no longer exists.
[How]
Check if the function declaration is NULL in disable stream encoder.
Security readout for executives and security teams
Plain-English summary
This Linux kernel flaw can crash systems when an AMD display stream is disabled. The business impact is availability, not data theft. The issue requires local access according to CVSS, so urgency is highest for Linux workstations, kiosks, or servers where display stability matters.
Executive priority
Treat as a moderate availability issue. Patch through normal kernel update cycles, accelerating for exposed workstations, display-dependent devices, or environments where local users can trigger system instability. There is no sourced evidence of active exploitation.
Technical view
CVE-2024-35799 is in drm/amd/display. Disabling a stream encoder may call a function that no longer exists, causing a crash. The fix checks whether the function declaration is NULL before use. CVSS 3.1 is 6.2, local attack vector, no privileges, no user interaction, availability high.
Likely exposure
Exposure is likely limited to Linux systems running affected kernel versions with the AMD display subsystem path present. The provided data lists Linux kernel versions including 4.15, 6.6.26, 6.7.12, 6.8.3, and 6.9 as affected, but distro backport status is not provided.
Exploitation context
The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. CVSS describes local exploitation with no privileges or user interaction, and the impact is a crash or denial of service rather than confidentiality or integrity compromise.
Researcher notes
The public description is concise and does not provide reproduction details. Analysis should focus on kernel commit presence, distro backports, AMD display code reachability, and crash telemetry. Avoid assuming remote exploitability or broader product exposure beyond Linux kernel drm/amd/display.
Mitigation direction
Apply kernel updates containing the referenced stable fixes.
Use distribution kernel packages rather than manual kernel changes where possible.
Prioritize systems dependent on AMD display stability.
Check vendor or distribution guidance for backported fixes.
Plan reboot windows if kernel replacement is required.
Validation and detection
Inventory Linux kernel versions across endpoints and servers.
Confirm whether AMD display drivers are present or in use.
Verify installed kernels include the referenced stable commits or distro backports.
Review vendor advisories for affected package mappings.
Monitor for display-related crashes after patch rollout.
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.
cwe · low confidence lookup
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-400 · source CWE mapping
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.