LiveActive security incident?Get immediate response
CVE Record

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.

MediumCVSS 6.2Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

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.
Prepared
Confidence
medium
Sources
6

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-35799 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

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.

1CVSS vectors
3Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
6.2CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H2.53.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

6.2Medium
CVSS 3.1 vector shape for CVE-2024-35799Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c, 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c, 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c, 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7cunaffected
LinuxLinux4.15, 0, 6.6.26, 6.7.12, 6.8.3, 6.9affected
Weakness

CWE details

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.