Skip to main content

CVE-2025-0072: CWE-416 Use After Free in Arm Ltd Valhall GPU Kernel Driver

High
VulnerabilityCVE-2025-0072cvecve-2025-0072cwe-416
Published: Fri May 02 2025 (05/02/2025, 09:54:20 UTC)
Source: CVE
Vendor/Project: Arm Ltd
Product: Valhall GPU Kernel Driver

Description

Use After Free vulnerability in Arm Ltd Valhall GPU Kernel Driver, Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver allows a local non-privileged user process to perform improper GPU memory processing operations to gain access to already freed memory. This issue affects Valhall GPU Kernel Driver: from r29p0 through r49p3, from r50p0 through r53p0; Arm 5th Gen GPU Architecture Kernel Driver: from r41p0 through r49p3, from r50p0 through r53p0.

AI-Powered Analysis

AILast updated: 07/12/2025, 03:48:15 UTC

Technical Analysis

CVE-2025-0072 is a Use After Free (UAF) vulnerability identified in the Arm Ltd Valhall GPU Kernel Driver, which is part of the Arm 5th Generation GPU Architecture. This vulnerability arises due to improper handling of GPU memory operations, where a local non-privileged user process can access memory that has already been freed. The affected driver versions span from r29p0 through r49p3 and from r50p0 through r53p0 for the Valhall GPU Kernel Driver, and similarly from r41p0 through r49p3 and r50p0 through r53p0 for the Arm 5th Gen GPU Architecture Kernel Driver. The vulnerability is classified under CWE-416, indicating a Use After Free condition, which can lead to serious security implications such as arbitrary code execution or privilege escalation. The CVSS v3.1 base score is 7.8, reflecting a high severity level. The attack vector is local (AV:L), requiring low attack complexity (AC:L) and low privileges (PR:L), but no user interaction (UI:N). The scope is unchanged (S:U), and the impact on confidentiality, integrity, and availability is high (C:H/I:H/A:H). This means an attacker with local access but limited privileges could exploit this flaw to gain unauthorized access to sensitive data, modify system integrity, or disrupt system availability. No known exploits are currently reported in the wild, and no patches or fixes have been linked yet. The vulnerability is significant because GPU drivers operate at the kernel level and have direct access to hardware resources, making exploitation potentially impactful on system stability and security.

Potential Impact

For European organizations, the impact of this vulnerability could be substantial, especially for those relying on devices or systems incorporating Arm 5th Gen GPUs, such as mobile devices, embedded systems, or specialized computing platforms. Successful exploitation could allow local attackers to escalate privileges, bypass security controls, or execute arbitrary code within the kernel context, leading to data breaches, system compromise, or denial of service. This is particularly critical for sectors with stringent data protection requirements, such as finance, healthcare, and critical infrastructure, where confidentiality and integrity are paramount. The local attack vector means that attackers would need some form of access to the device, which could be achieved through compromised user accounts or malicious insiders. Given the high impact on confidentiality, integrity, and availability, organizations could face regulatory consequences under GDPR if personal data is exposed or systems are disrupted. Additionally, the lack of current patches increases the window of exposure, necessitating immediate risk mitigation.

Mitigation Recommendations

To mitigate this vulnerability effectively, European organizations should: 1) Identify and inventory all devices and systems using Arm 5th Gen GPUs with the affected driver versions to understand exposure. 2) Restrict local access to trusted users only, employing strict access controls and monitoring for unusual local activity. 3) Implement application whitelisting and endpoint detection and response (EDR) solutions to detect and prevent exploitation attempts. 4) Employ kernel-level integrity monitoring to detect anomalous behavior related to GPU driver operations. 5) Engage with Arm Ltd and device vendors to obtain and deploy patches or firmware updates as soon as they become available. 6) Consider temporary mitigations such as disabling GPU acceleration features in high-risk environments if feasible. 7) Conduct user awareness training to reduce the risk of local compromise that could lead to exploitation. 8) Monitor security advisories and threat intelligence feeds for any emerging exploit information or updated mitigation guidance.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Arm
Date Reserved
2024-12-13T13:18:00.462Z
Cisa Enriched
true
Cvss Version
3.1
State
PUBLISHED

Threat ID: 682d9816c4522896dcbd6ba0

Added to database: 5/21/2025, 9:08:38 AM

Last enriched: 7/12/2025, 3:48:15 AM

Last updated: 8/7/2025, 9:04:10 AM

Views: 20

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

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