Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-0010: CWE-787 Out-of-bounds Write in AMD AMD Radeon™ RX 5000 Series Graphics Products

0
Medium
VulnerabilityCVE-2025-0010cvecve-2025-0010cwe-787
Published: Sat Sep 06 2025 (09/06/2025, 18:26:15 UTC)
Source: CVE Database V5
Vendor/Project: AMD
Product: AMD Radeon™ RX 5000 Series Graphics Products

Description

An out of bounds write in the Linux graphics driver could allow an attacker to overflow the buffer potentially resulting in loss of confidentiality, integrity, or availability.

AI-Powered Analysis

AILast updated: 09/15/2025, 00:41:14 UTC

Technical Analysis

CVE-2025-0010 is a medium-severity vulnerability classified under CWE-787 (Out-of-bounds Write) affecting AMD Radeon™ RX 5000 Series graphics products specifically on Linux platforms. The vulnerability arises from an out-of-bounds write condition in the Linux graphics driver for these GPUs, which could allow an attacker with limited privileges (local access with low complexity) and requiring user interaction to overflow a buffer. This buffer overflow can lead to corruption of adjacent memory, potentially causing loss of confidentiality, integrity, or availability of the system. The vulnerability's CVSS v3.1 base score is 6.1, reflecting that it requires local access and user interaction but has a significant impact on availability and some impact on confidentiality and integrity. The scope remains unchanged, meaning the vulnerability affects only the vulnerable component without spreading to other components. No known exploits are currently reported in the wild, and no patches have been linked yet, indicating that mitigation may rely on vendor updates once available. The vulnerability is particularly relevant for Linux systems using AMD Radeon RX 5000 Series GPUs, which are common in workstations and some enterprise environments. Exploitation could allow attackers to cause system crashes, denial of service, or potentially escalate privileges by corrupting memory, depending on the context of the overflow and the privileges of the attacker. Given the requirement for local access and user interaction, remote exploitation is not feasible without prior compromise or social engineering.

Potential Impact

For European organizations, this vulnerability poses a moderate risk primarily to environments running Linux with AMD Radeon RX 5000 Series GPUs, such as research institutions, media companies, and enterprises using these GPUs for compute or graphical workloads. The potential impacts include system instability, denial of service, and possible data corruption or leakage if the out-of-bounds write is leveraged to manipulate sensitive information in memory. Confidentiality and integrity impacts are rated low to medium, but availability impact is high due to the possibility of system crashes. Organizations relying on these GPUs for critical workloads could face operational disruptions. Additionally, if attackers gain local access through other means, this vulnerability could be chained to escalate privileges or maintain persistence. The requirement for user interaction limits the attack surface but does not eliminate risk, especially in environments with multiple users or where social engineering is possible. The absence of known exploits reduces immediate risk but emphasizes the need for proactive mitigation.

Mitigation Recommendations

European organizations should implement the following specific mitigations: 1) Monitor AMD and Linux distribution security advisories closely for patches addressing this vulnerability and apply updates promptly once available. 2) Restrict local access to systems with AMD Radeon RX 5000 Series GPUs to trusted users only, employing strict access controls and user authentication mechanisms. 3) Employ endpoint protection solutions capable of detecting anomalous behavior indicative of exploitation attempts, such as unusual buffer overflow attempts or crashes related to graphics drivers. 4) Educate users about the risks of social engineering and the importance of not interacting with untrusted applications or files that could trigger the vulnerability. 5) Consider isolating critical systems using these GPUs in segmented network zones to limit lateral movement in case of compromise. 6) Regularly audit and harden Linux systems, disabling unnecessary services and ensuring minimal user privileges to reduce the attack surface. 7) Use kernel-level exploit mitigations such as Address Space Layout Randomization (ASLR) and stack canaries to make exploitation more difficult. These measures, combined with timely patching, will reduce the risk posed by this vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
AMD
Date Reserved
2024-10-10T20:27:46.721Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68bccd0da2c363fb16078f99

Added to database: 9/7/2025, 12:08:45 AM

Last enriched: 9/15/2025, 12:41:14 AM

Last updated: 10/22/2025, 5:29:28 AM

Views: 35

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats