CVE-2024-46818: drm/amd/display: Check gpio_id before used as array index
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Check gpio_id before used as array index
[WHY & HOW]
GPIO_ID_UNKNOWN (-1) is not a valid value for array index and therefore
should be checked in advance.
This fixes 5 OVERRUN issues reported by Coverity.
Security readout for executives and security teams
Plain-English summary
A Linux AMD display-driver flaw can use an invalid GPIO identifier as an array index, causing memory overruns. The supplied CVSS rating is 7.8 (high): exploitation requires low-privileged local access but no user interaction, with potentially serious confidentiality, integrity, and availability impact.
Executive priority
Treat this as a high-priority endpoint and workstation remediation item, not an unauthenticated internet emergency. Accelerate patching where untrusted or numerous local users can access AMD-graphics Linux systems. Validate exposure before escalating headless or unrelated systems.
Technical view
Within drm/amd/display, GPIO_ID_UNKNOWN (-1) could reach an array access without prior validation. The Linux fix checks gpio_id before indexing. Coverity identified five overrun instances. The CVSS vector indicates local attack access, low complexity, low privileges, unchanged scope, and high modeled impact across confidentiality, integrity, and availability.
Likely exposure
Exposure is most likely on systems running an affected Linux kernel where the AMD display component and relevant hardware path are present. Workstations and other locally accessible AMD-graphics systems deserve priority. The supplied version data does not preserve clear range boundaries, so distribution-specific kernel mapping is necessary.
Exploitation context
The supplied record indicates a local, low-privilege attack vector with no user interaction. It does not establish a practical exploitation method or precondition beyond the affected driver condition. The CVE is not marked as KEV, and no included source reports active exploitation.
Researcher notes
The underlying defect is an unchecked negative sentinel used as an array index, with five overruns reported by Coverity. Seven stable-tree fixes are referenced. Exact affected and corrected release boundaries are ambiguous in the supplied normalized version list; use the CVE record, stable commits, and distribution advisories for branch-specific conclusions.
Mitigation direction
Install a distribution-supported kernel update incorporating the applicable upstream stable fix.
Reboot affected systems into the updated kernel after installation.
Consult the Linux distribution's advisory when package-to-upstream version mapping is unclear.
Prioritize locally accessible systems with AMD graphics and the affected display component.
Validation and detection
Inventory running kernel builds and AMD graphics hardware across Linux systems.
Determine whether the drm/amd/display component is present and active on each candidate system.
Map distribution kernel packages to the applicable upstream stable fix or vendor advisory.
After updating and rebooting, confirm the running kernel contains the correction.
Re-scan affected assets and investigate any remaining detections against vendor version guidance.
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-46818 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.