CVE-2024-46815: drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[]
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[]
[WHY & HOW]
num_valid_sets needs to be checked to avoid a negative index when
accessing reader_wm_sets[num_valid_sets - 1].
This fixes an OVERRUN issue reported by Coverity.
Security readout for executives and security teams
Plain-English summary
A flaw in Linux's AMD display driver can access memory outside the intended array when no valid watermark sets exist. A local user with limited privileges may be able to disrupt the system or alter protected data. The supplied CVSS score is 7.1; no confidentiality impact is claimed.
Executive priority
Treat as a high-priority local privilege-boundary issue, especially on multi-user AMD graphics systems. It does not warrant internet-emergency handling based on the supplied evidence, but timely kernel patching is appropriate because integrity and availability impacts are rated high.
Technical view
The AMD DRM display code accessed reader_wm_sets[num_valid_sets - 1] without first ensuring num_valid_sets was positive, allowing a negative array index and overrun. The kernel fix adds the missing bounds check. The CVSS vector indicates local, low-complexity, low-privilege exploitation with high integrity and availability impact.
Likely exposure
Exposure is limited to Linux systems running affected kernel code in the AMD display stack. It is not described as remotely exploitable. The supplied version data is ambiguous, so determine exposure using distribution advisories and whether the AMD display driver is present and active.
Exploitation context
The source bundle does not establish active exploitation, and the CVE is not listed as KEV. It also provides no evidence of a public exploit. Successful exploitation requires local access with low privileges according to the supplied CVSS vector.
Researcher notes
Coverity identified an overrun caused by indexing with num_valid_sets minus one when the count could be zero. Multiple stable-kernel commits are referenced, likely reflecting branch-specific backports. Exact vulnerable ranges and practical exploitability are not fully established by the supplied material; validate against the relevant distribution's package advisory.
Mitigation direction
Install the vendor-supported kernel update containing the relevant stable-branch fix.
Reboot affected systems so the corrected kernel becomes active.
Consult distribution guidance where the supplied affected-version data is ambiguous.
Prioritize shared workstations or other systems where untrusted users have local access.
Validation and detection
Inventory Linux systems using AMD graphics and the AMD display driver.
Record each running kernel version, not only the installed package version.
Compare versions against the applicable distribution advisory and stable-branch fix.
After updating and rebooting, confirm the corrected kernel is running.
Monitor affected systems for display-driver faults, crashes, or unexplained instability.
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-46815 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.