LiveActive security incident?Get immediate response
CVE Record

CVE-2024-35952: drm/ast: Fix soft lockup

In the Linux kernel, the following vulnerability has been resolved: drm/ast: Fix soft lockup There is a while-loop in ast_dp_set_on_off() that could lead to infinite-loop. This is because the register, VGACRI-Dx, checked in this API is a scratch register actually controlled by a MCU, named DPMCU, in BMC. These scratch registers are protected by scu-lock. If suc-lock is not off, DPMCU can not update these registers and then host will have soft lockup due to never updated status. DPMCU is used to control DP and relative registers to handshake with host's VGA driver. Even the most time-consuming task, DP's link training, is less than 100ms. 200ms should be enough.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-35952 is a Linux kernel availability flaw in the AST display driver. A driver loop can wait forever for a BMC-controlled status register, causing a host soft lockup. The business risk is service disruption on affected Linux systems using this driver, not data theft or remote code execution based on the provided sources.

Executive priority

Treat this as a targeted availability issue. Patch during normal urgent kernel maintenance for systems using AST/BMC display paths, especially infrastructure where host lockups affect service continuity. It does not warrant emergency internet-facing RCE handling based on the provided evidence.

Technical view

The flaw is in drm/ast ast_dp_set_on_off(). It polls VGACRI-Dx, a scratch register controlled by the BMC DPMCU. If the scu-lock prevents DPMCU updates, the host can loop indefinitely. The upstream fix bounds the wait; the source notes DPMCU DisplayPort work should complete under 100ms and 200ms is sufficient.

Likely exposure

Exposure is most likely on affected Linux kernels using the AST DRM driver, especially systems with BMC-managed display hardware and DisplayPort handling. The provided CVE data lists Linux versions including 5.19, 6.1.87, 6.6.28, 6.8.7, and 6.9 as affected, but exact distribution package status must be verified with vendors.

Exploitation context

The source bundle does not cite active exploitation, and KEV is false. No public exploit status is provided. The described impact is a kernel soft lockup caused by driver and BMC register handshaking failure, so exploitation context appears local or hardware-path dependent rather than broad network exposure.

Researcher notes

No CVSS, CWE, or exploit evidence is supplied. The key behavior is an unbounded wait on a BMC-updated scratch register protected by scu-lock. Validation should focus on driver reachability, kernel branch fix status, and whether operational display paths can trigger ast_dp_set_on_off().

Mitigation direction

  • Update affected Linux kernels to vendor builds containing the referenced stable fixes.
  • Check Linux distribution advisories for package-specific fixed kernel versions.
  • Prioritize systems using the AST DRM driver or BMC-managed display hardware.
  • If no update is available, follow vendor guidance for temporary operational controls.

Validation and detection

  • Inventory kernel versions against the affected Linux versions in the CVE record.
  • Confirm whether the AST DRM driver is present or loaded on target systems.
  • Verify kernel changelogs include one of the referenced stable fix commits.
  • Review kernel logs for soft lockup messages around AST display activity.
Prepared
Confidence
medium
Sources
6

Public sources used

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-35952 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

SSVC decision data

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

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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux594e9c04b5864b4b8b151ef4ba9521c59e0f5c54, 594e9c04b5864b4b8b151ef4ba9521c59e0f5c54, 594e9c04b5864b4b8b151ef4ba9521c59e0f5c54, 594e9c04b5864b4b8b151ef4ba9521c59e0f5c54unaffected
LinuxLinux5.19, 0, 6.1.87, 6.6.28, 6.8.7, 6.9affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.