In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: Fix out-of-bounds write warning
Check the ring type value to fix the out-of-bounds
write warning
Security readout for executives and security teams
Plain-English summary
A flaw in the Linux AMD GPU driver can write outside an intended memory boundary when processing an invalid ring type. A local, low-privileged user may be able to trigger serious confidentiality, integrity, or availability impacts. Systems without the AMDGPU driver or affected kernel code are unlikely to be exposed.
Executive priority
Treat as a prompt patching priority for exposed AMD GPU systems, especially shared hosts where untrusted local users have accounts. It is not supported as an emergency internet-wide threat because exploitation requires local access and active exploitation is not documented.
Technical view
The drm/amdgpu code did not adequately validate a ring-type value, producing an out-of-bounds write warning. The kernel fix adds a ring-type check. CVSS 3.1 rates the issue 7.8: local access, low complexity, low privileges, no user interaction, and potentially high confidentiality, integrity, and availability impact.
Likely exposure
Prioritize Linux workstations, GPU compute hosts, and multi-user systems that load amdgpu while running affected kernel builds. The supplied version data does not establish complete distribution-specific package ranges, so compare the active kernel against vendor advisories and fixed commits.
Exploitation context
The supplied record does not identify CISA KEV listing or active exploitation. The CVSS vector describes local, low-privileged access rather than remote exploitation. No public exploit evidence is provided in the source bundle.
Researcher notes
The public description is terse and provides no reproducer, affected call path, CWE, or demonstrated impact. Multiple stable-tree commits indicate backports across kernel lines. Exact exposure should be established by commit or distribution package status, not version-string assumptions.
Mitigation direction
Install a vendor-supported kernel package containing the applicable upstream stable fix.
Reboot into the updated kernel so the corrected amdgpu code becomes active.
Prioritize shared or untrusted-user systems with AMD GPUs.
Consult distribution guidance where fixed package status is unclear.
Validation and detection
Record the running kernel version and distribution package revision.
Confirm whether the amdgpu module is present and loaded.
Compare the active package with vendor advisories and applicable stable commits.
After reboot, verify the patched kernel is running.
Review kernel logs for recurring amdgpu out-of-bounds warnings.
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-46725 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.