CVE-2024-26922: drm/amdgpu: validate the parameters of bo mapping operations more clearly
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: validate the parameters of bo mapping operations more clearly
Verify the parameters of
amdgpu_vm_bo_(map/replace_map/clearing_mappings) in one common place.
Security readout for executives and security teams
Plain-English summary
A Linux kernel flaw in the AMDGPU graphics driver insufficiently validated parameters used when mapping GPU buffer objects. A local, low-privileged user could potentially compromise confidentiality, integrity, and availability. Exposure depends on the affected kernel code being present and relevant AMDGPU functionality being accessible.
Executive priority
Treat as a high-priority local privilege-boundary risk, not an internet-wide emergency. Patch exposed shared or untrusted-user systems promptly, then address remaining affected AMDGPU hosts through normal high-severity maintenance. Escalate if local compromise would expose sensitive workloads or critical operations.
Technical view
CVE-2024-26922 affects parameter validation across amdgpu_vm_bo_map, amdgpu_vm_bo_replace_map, and clearing-mapping operations. The kernel fix consolidates validation in one place. The supplied CVSS 3.1 score is 7.8: local access, low complexity, low privileges, no user interaction, and potentially high confidentiality, integrity, and availability impact.
Likely exposure
Prioritize Linux systems running affected kernel versions where AMDGPU functionality is present or used, especially multi-user endpoints and compute hosts. The bundle lists affected releases from 4.12 through 6.9, with fixed stable versions including 4.19.313, 5.4.275, 5.10.216, 5.15.157, 6.1.88, 6.6.29, and 6.8.8. Distribution backports may alter exposure.
Exploitation context
The supplied CVSS vector requires local access and low privileges; this is not described as a remotely exploitable flaw. CISA KEV status is false, and the provided sources do not establish active exploitation, public exploit availability, or a demonstrated attack chain.
Researcher notes
The public description identifies inadequate mapping-parameter validation but does not provide a CWE, detailed memory-safety mechanism, crash evidence, or proven exploitation primitive. Multiple stable-tree commits indicate backports across kernel branches. Researchers should assess exact branch ancestry and distribution backports before declaring a system vulnerable; version strings alone may misclassify patched vendor kernels.
Mitigation direction
Apply the latest supported kernel update supplied by your Linux distribution.
Confirm the update includes the CVE fix or an equivalent vendor backport.
Prioritize shared systems where untrusted local users can access AMDGPU functionality.
Consult distribution or kernel vendor guidance when version or backport status is unclear.
Validation and detection
Inventory running kernel versions and identify systems using AMDGPU hardware or drivers.
Compare each distribution kernel against its vendor advisory and fixed package release.
Verify the corrected kernel is running after maintenance, not merely installed.
For custom kernels, confirm inclusion of the applicable upstream stable fix commit.
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-26922 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.