Security readout for executives and security teams
Plain-English summary
A flaw in the Linux AMD graphics display driver can overrun an internal link array during driver initialization when the detected link count exceeds its limit. A successful local attack could compromise confidentiality, integrity, and availability. Exposure appears limited to systems using the affected AMD display path, but the supplied records do not fully define practical trigger conditions.
Executive priority
Treat as a high-priority kernel maintenance issue for AMD GPU systems, especially multi-user endpoints or graphics servers. It does not warrant the urgency of an internet-exploited vulnerability because local access is required and active exploitation is unsupported. Complete exposure mapping promptly, then deploy vendor-confirmed kernel updates through normal expedited patching controls.
Technical view
The amdgpu_dm initialization path allowed a link count up to 31 while dc->links contained only max_links elements. This mismatch produced an out-of-bounds access risk identified by Coverity. The kernel fix stops initialization when the link count exceeds max_links. CVSS 3.1 rates it 7.8: local, low complexity, low privileges, no user interaction, and high impact.
Likely exposure
Prioritize Linux workstations, graphics servers, and other systems using AMD GPUs with the amdgpu display driver. The supplied affected-version data is ambiguous and includes several kernel versions without clear range boundaries. Systems without the relevant AMD display path are less likely to be exposed, but downstream vendor patch status must be checked.
Exploitation context
The CVSS vector indicates exploitation requires local access and low privileges; it is not described as remotely exploitable. CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a public exploit. Real-world reachability may depend on AMD display hardware, driver initialization, and an excessive detected link count.
Researcher notes
The source describes a bounds-check failure in drm/amd/display during amdgpu_dm initialization. It does not identify a CWE, demonstrated exploit, specific triggering hardware topology, or confirmed exploitation. The duplicated commit identifier and flattened affected-version list reduce precision; assess downstream kernels by patch inclusion rather than version-string comparison alone.
Mitigation direction
- Install a vendor-supported kernel containing the applicable referenced stable fix.
- Check distribution advisories for backported fixes instead of relying only on upstream version numbers.
- Prioritize shared or untrusted-user systems with AMD graphics and the amdgpu display driver.
- Restrict local account access until affected systems receive a confirmed patched kernel.
Validation and detection
- Inventory running kernel versions and identify systems using AMD graphics hardware.
- Confirm whether the amdgpu display driver is active on each candidate system.
- Map distribution kernel builds to vendor advisories or referenced upstream fix commits.
- After updating, verify the running kernel build includes the applicable backport.
- Review kernel logs for abnormal AMD display initialization failures or crashes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2024-46816 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/e2411b6abf6e5d6c33d0450846673cdf536f0ba4CVE reference, Linux
- https://git.kernel.org/stable/c/e3cd0d8362de47f613bfdf315b3f3a9ab71e66bfCVE reference, Linux
- https://git.kernel.org/stable/c/13080d052c995aee14695a5b740c245121eb2bccCVE reference, Linux
- https://git.kernel.org/stable/c/c84632096722fd31251f0957fafc9e90d9a247fdCVE reference, Linux
- https://git.kernel.org/stable/c/36c39a8dcce210649f2f45f252abaa09fcc1ae87CVE reference, Linux
- https://git.kernel.org/stable/c/cf8b16857db702ceb8d52f9219a4613363e2b1cfCVE reference, Linux
- https://lists.debian.org/debian-lts-announce/2025/05/msg00045.htmlCVE reference, CVE
- https://lists.debian.org/debian-lts-announce/2025/05/msg00030.htmlCVE reference, CVE
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.