LiveActive security incident?Get immediate response
CVE Record

CVE-2024-35786: drm/nouveau: fix stale locked mutex in nouveau_gem_ioctl_pushbuf

In the Linux kernel, the following vulnerability has been resolved: drm/nouveau: fix stale locked mutex in nouveau_gem_ioctl_pushbuf If VM_BIND is enabled on the client the legacy submission ioctl can't be used, however if a client tries to do so regardless it will return an error. In this case the clients mutex remained unlocked leading to a deadlock inside nouveau_drm_postclose or any other nouveau ioctl call.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects the nouveau DRM component. A client using VM_BIND could trigger an error path in a legacy submission ioctl that leaves mutex handling in a bad state, causing later close or ioctl operations to deadlock. The business impact appears to be availability, not data theft, based on the supplied sources.

Executive priority

Treat this as a moderate availability issue. It is not presented as remotely exploitable or actively exploited, but affected Linux GPU workloads could hang driver operations. Patch through normal kernel maintenance, with higher priority for systems relying on nouveau.

Technical view

CVE-2024-35786 is a resolved Linux kernel nouveau bug in nouveau_gem_ioctl_pushbuf. When VM_BIND is enabled, legacy submission ioctl use should fail, but the failure path left client mutex state stale, leading to deadlock in nouveau_drm_postclose or later nouveau ioctl calls. Stable kernel commits are listed as references.

Likely exposure

Exposure is most likely on Linux systems running affected kernel versions with the nouveau DRM driver path in use. The source lists Linux kernel 6.6-era affected data and stable commit references, but does not provide distribution package names or complete platform details.

Exploitation context

The supplied bundle does not show active exploitation, public exploit code, or CISA KEV listing. The described trigger requires a local client interaction with nouveau ioctl behavior, so available evidence points to local denial-of-service risk rather than remote compromise.

Researcher notes

Evidence is limited to the CVE text and kernel stable references. The affected-version data is not distro-specific and appears branch-oriented. Validate against the actual kernel tree or vendor advisory before declaring exposure or non-exposure.

Mitigation direction

  • Apply Linux kernel updates containing the referenced stable fixes.
  • Check distribution advisories for backported fixes to your deployed kernel packages.
  • Prioritize systems using nouveau DRM functionality or affected kernel branches.
  • If no vendor package is available, follow vendor kernel mitigation guidance.

Validation and detection

  • Inventory Linux kernel versions across relevant systems.
  • Identify hosts using the nouveau DRM component.
  • Compare deployed kernels against vendor advisories and referenced stable commits.
  • Confirm update status through distribution package metadata.
  • Monitor for recurring nouveau-related deadlocks or GPU driver hangs.
Prepared
Confidence
medium
Sources
5

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-35786 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
4Source 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

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxb88baab828713ce0b49b185444b2ee83bed373a8, b88baab828713ce0b49b185444b2ee83bed373a8, b88baab828713ce0b49b185444b2ee83bed373a8unaffected
LinuxLinux6.6, 0, 6.6.24, 6.7.12, 6.8affected
Weakness

CWE details

No CWE listed

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