CVE-2024-35950: drm/client: Fully protect modes[] with dev->mode_config.mutex
In the Linux kernel, the following vulnerability has been resolved:
drm/client: Fully protect modes[] with dev->mode_config.mutex
The modes[] array contains pointers to modes on the connectors'
mode lists, which are protected by dev->mode_config.mutex.
Thus we need to extend modes[] the same protection or by the
time we use it the elements may already be pointing to
freed/reused memory.
Security readout for executives and security teams
Plain-English summary
CVE-2024-35950 is a Linux kernel graphics/display bug. Kernel DRM client code could use pointers after associated display modes were freed or reused because locking did not fully cover modes[]. Business urgency depends on running affected kernels and vendor advisories; the source data gives no CVSS score or confirmed exploitation.
Executive priority
Monitor and patch through normal kernel maintenance unless vendor guidance elevates risk for your environment. Escalate priority for exposed appliances, shared systems, or products named by vendor advisories.
Technical view
The issue is in drm/client handling of modes[]. The array contains pointers into connector mode lists protected by dev->mode_config.mutex. The fix extends that protection so modes[] entries are not used after the underlying mode objects may have been freed or reused.
Likely exposure
Exposure is likely limited to Linux systems running affected kernel versions with the DRM display stack present. The bundle lists Linux kernel versions and stable fixes, plus Debian LTS and Siemens references, but does not provide complete product-level impact details.
Exploitation context
The provided sources do not show CISA KEV listing, public exploitation, exploit maturity, CVSS, or attack vector. Treat this as a kernel memory-safety issue requiring patch tracking, not as confirmed active exploitation.
Researcher notes
Evidence supports a DRM locking lifetime bug involving modes[] pointers and dev->mode_config.mutex. Impact boundaries are not fully described in the bundle, so avoid assuming privilege escalation, remote reachability, or denial-of-service without additional vendor evidence.
Mitigation direction
Update to a vendor kernel containing the referenced stable DRM fixes.
Follow Debian LTS guidance for Debian-based affected systems.
Check Siemens SSA-265688 for any impacted Siemens product guidance.
Prioritize internet-managed or shared-user Linux systems after vendor impact confirmation.
Validation and detection
Inventory Linux kernel versions across servers, workstations, appliances, and embedded assets.
Confirm whether assets use affected Linux kernel builds listed by the CVE record.
Verify installed kernel packages include the relevant upstream stable commits.
Review vendor advisories for distribution-specific fixed package versions.
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-35950 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.