CVE-2024-35810: drm/vmwgfx: Fix the lifetime of the bo cursor memory
In the Linux kernel, the following vulnerability has been resolved:
drm/vmwgfx: Fix the lifetime of the bo cursor memory
The cleanup can be dispatched while the atomic update is still active,
which means that the memory acquired in the atomic update needs to
not be invalidated by the cleanup. The buffer objects in vmw_plane_state
instead of using the builtin map_and_cache were trying to handle
the lifetime of the mapped memory themselves, leading to crashes.
Use the map_and_cache instead of trying to manage the lifetime of the
buffer objects held by the vmw_plane_state.
Fixes kernel oops'es in IGT's kms_cursor_legacy forked-bo.
Security readout for executives and security teams
Plain-English summary
A Linux graphics-driver memory-lifetime flaw can cause kernel crashes when cursor display updates overlap cleanup. Exploitation requires local, low-privileged access according to CVSS. Because kernel failure may disrupt systems and the CVSS assessment indicates possible confidentiality and integrity impact, affected hosts should be patched promptly.
Executive priority
Treat as a high-priority kernel maintenance issue on systems using vmwgfx. Patch exposed multi-user or locally accessible hosts first. Broader emergency action is not supported because exploitation is local and no active exploitation evidence is supplied.
Technical view
The vmwgfx DRM driver manually managed mapped buffer-object memory in vmw_plane_state. Cleanup could invalidate that memory while an atomic cursor update remained active, producing kernel oopses. The upstream correction uses the existing map_and_cache lifetime mechanism. The supplied record identifies affected Linux kernel releases beginning with 6.2 and provides four stable-branch correction commits.
Likely exposure
Exposure is limited to systems running an affected Linux kernel with the vmwgfx driver in use. The supplied version data lists 6.2, 6.6.24, 6.7.12, 6.8.3, and 6.9, but does not clearly define every affected range or distribution backport.
Exploitation context
The CVSS vector describes a local, low-complexity attack requiring low privileges and no user interaction. The documented outcome is kernel crashes during cursor-related testing. The record is not in KEV, and the supplied sources provide no evidence of active exploitation or a public exploit.
Researcher notes
The described flaw is a mapped-memory lifetime race between atomic cursor updates and cleanup. IGT's kms_cursor_legacy forked-bo test reportedly triggered kernel oopses. No CWE is assigned. The supplied CVSS claims high confidentiality, integrity, and availability impact, although the narrative directly confirms crashes only; further impact is not demonstrated here.
Mitigation direction
Install a vendor-supported kernel containing the applicable stable correction commit.
Check distribution security guidance for exact fixed package versions and backports.
Prioritize systems using vmwgfx, especially shared or locally accessible workloads.
Where immediate patching is impossible, reduce untrusted local access pending vendor guidance.
Validation and detection
Inventory kernel versions and determine whether vmwgfx is loaded or operationally required.
Confirm the installed kernel includes the relevant stable-branch correction or vendor backport.
Review kernel logs for vmwgfx-related oopses or cursor-update crashes.
After updating, run approved regression tests covering display and cursor operations.
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-35810 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.
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.