CVE-2024-42275: drm/client: Fix error code in drm_client_buffer_vmap_local()
In the Linux kernel, the following vulnerability has been resolved:
drm/client: Fix error code in drm_client_buffer_vmap_local()
This function accidentally returns zero/success on the failure path.
It leads to locking issues and an uninitialized *map_copy in the
caller.
Security readout for executives and security teams
Plain-English summary
A Linux graphics subsystem function can mistakenly report success after a buffer-mapping failure. The caller may then use uninitialized mapping data and encounter locking problems. The supplied CVSS assessment rates potential confidentiality, integrity, and availability impact as high, but exploitation requires local, low-privileged access.
Executive priority
Treat as a high-priority kernel update for exposed multi-user or shared-compute systems. Internet-only attackers cannot directly exercise the stated local vector, but an existing low-privileged foothold could increase business impact. Schedule prompt remediation through normal tested kernel-update procedures.
Technical view
CVE-2024-42275 affects drm_client_buffer_vmap_local() in the Linux DRM client code. Its failure path returns zero, causing callers to treat a failed mapping as successful. This can leave map_copy uninitialized and create locking issues. The supplied CVSS v3.1 score is 7.8 with a local, low-complexity, low-privilege vector.
Likely exposure
Systems running affected 6.10-era Linux kernels with the vulnerable DRM code may be exposed, particularly where untrusted local users or workloads can interact with graphics functionality. The supplied version metadata is not sufficiently clear to determine every affected or fixed release; distribution backports must be checked individually.
Exploitation context
The supplied record does not establish active exploitation, and CVE-2024-42275 is not marked as CISA KEV. The CVSS vector describes local access with low privileges, no user interaction, and potentially high confidentiality, integrity, and availability impact. No evidence in the bundle confirms a public working exploit.
Researcher notes
The core defect is failure-signaling corruption rather than a documented standalone privilege-escalation primitive. Security impact follows from an uninitialized map_copy and locking inconsistencies after callers receive false success. The bundle provides no demonstrated exploitation chain, affected hardware requirements, or complete distribution-specific version mapping.
Mitigation direction
Apply a vendor-supported kernel containing the referenced stable fix.
Check distribution advisories for backported fixes and exact affected package versions.
Prioritize multi-user systems and hosts running untrusted local workloads.
Restrict unnecessary local access until affected kernels are updated.
Validation and detection
Record each host's running kernel and distribution package version.
Compare versions against the applicable distribution security advisory.
Confirm the installed kernel incorporates one of the referenced stable fixes.
Reboot after updating and verify the fixed kernel is running.
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-42275 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.