CVE-2024-4610: CWE-416 Use After Free in Arm Ltd Bifrost GPU Kernel Driver
Use After Free vulnerability in Arm Ltd Bifrost GPU Kernel Driver, Arm Ltd Valhall GPU Kernel Driver allows a local non-privileged user to make improper GPU memory processing operations to gain access to already freed memory.This issue affects Bifrost GPU Kernel Driver: from r34p0 through r40p0; Valhall GPU Kernel Driver: from r34p0 through r40p0.
AI Analysis
Technical Summary
CVE-2024-4610 is a Use After Free (CWE-416) vulnerability identified in Arm Ltd's Bifrost and Valhall GPU Kernel Drivers, specifically versions from r34p0 through r40p0. The flaw arises when a local non-privileged user triggers improper GPU memory processing operations that access memory regions already freed by the kernel driver. This can lead to unauthorized access to sensitive data, corruption of memory, or arbitrary code execution within the kernel context. The vulnerability affects the GPU kernel drivers responsible for managing GPU memory and operations on Arm-based devices, including many smartphones, tablets, and embedded systems. The CVSS v3.1 base score is 7.4, indicating high severity, with the vector AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, meaning the attack requires local access with high complexity, no privileges, and no user interaction, but can cause high impact on confidentiality, integrity, and availability. No public exploits are known yet, but the potential for privilege escalation and system compromise is significant. The issue is critical for environments where local user access is possible, such as multi-user systems or devices exposed to untrusted users. The vulnerability was published on June 7, 2024, and no patches have been linked yet, emphasizing the need for vigilance and prompt remediation once fixes are released.
Potential Impact
The vulnerability allows a local attacker to exploit the GPU kernel driver to access freed memory, potentially leading to leakage of sensitive information, corruption of kernel memory, or execution of arbitrary code with kernel privileges. This can result in full system compromise, including bypassing security controls, escalating privileges, and disrupting system availability. For organizations, this means that any system running affected Arm GPU drivers is at risk if local access is gained by an attacker or malicious insider. The impact is particularly severe in multi-user environments, shared devices, or scenarios where local access controls are weak. Confidentiality breaches could expose sensitive data processed by the GPU, while integrity and availability impacts could disrupt critical applications relying on GPU acceleration. Since Arm GPUs are widely used in mobile and embedded devices, this vulnerability could affect a broad range of consumer and enterprise devices, potentially undermining trust in device security and leading to costly incident response and remediation efforts.
Mitigation Recommendations
1. Monitor Arm Ltd's official channels for patches addressing CVE-2024-4610 and apply them promptly once available. 2. Restrict local access to trusted users only, minimizing the risk of exploitation by unprivileged users. 3. Implement strict access controls and user privilege management on devices using affected GPU drivers. 4. Employ runtime security tools capable of detecting anomalous GPU memory operations or kernel driver misuse. 5. For enterprise environments, consider isolating critical systems or enforcing endpoint security policies that limit local code execution capabilities. 6. Conduct regular security audits focusing on kernel driver integrity and GPU-related processes. 7. Educate users and administrators about the risks of local access vulnerabilities and the importance of applying updates. 8. If possible, disable or limit GPU kernel driver features not required for normal operation until patches are applied. These steps go beyond generic advice by focusing on controlling local access vectors and monitoring GPU-specific behaviors.
Affected Countries
United States, China, India, South Korea, Japan, Germany, United Kingdom, France, Taiwan, Canada
CVE-2024-4610: CWE-416 Use After Free in Arm Ltd Bifrost GPU Kernel Driver
Description
Use After Free vulnerability in Arm Ltd Bifrost GPU Kernel Driver, Arm Ltd Valhall GPU Kernel Driver allows a local non-privileged user to make improper GPU memory processing operations to gain access to already freed memory.This issue affects Bifrost GPU Kernel Driver: from r34p0 through r40p0; Valhall GPU Kernel Driver: from r34p0 through r40p0.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2024-4610 is a Use After Free (CWE-416) vulnerability identified in Arm Ltd's Bifrost and Valhall GPU Kernel Drivers, specifically versions from r34p0 through r40p0. The flaw arises when a local non-privileged user triggers improper GPU memory processing operations that access memory regions already freed by the kernel driver. This can lead to unauthorized access to sensitive data, corruption of memory, or arbitrary code execution within the kernel context. The vulnerability affects the GPU kernel drivers responsible for managing GPU memory and operations on Arm-based devices, including many smartphones, tablets, and embedded systems. The CVSS v3.1 base score is 7.4, indicating high severity, with the vector AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, meaning the attack requires local access with high complexity, no privileges, and no user interaction, but can cause high impact on confidentiality, integrity, and availability. No public exploits are known yet, but the potential for privilege escalation and system compromise is significant. The issue is critical for environments where local user access is possible, such as multi-user systems or devices exposed to untrusted users. The vulnerability was published on June 7, 2024, and no patches have been linked yet, emphasizing the need for vigilance and prompt remediation once fixes are released.
Potential Impact
The vulnerability allows a local attacker to exploit the GPU kernel driver to access freed memory, potentially leading to leakage of sensitive information, corruption of kernel memory, or execution of arbitrary code with kernel privileges. This can result in full system compromise, including bypassing security controls, escalating privileges, and disrupting system availability. For organizations, this means that any system running affected Arm GPU drivers is at risk if local access is gained by an attacker or malicious insider. The impact is particularly severe in multi-user environments, shared devices, or scenarios where local access controls are weak. Confidentiality breaches could expose sensitive data processed by the GPU, while integrity and availability impacts could disrupt critical applications relying on GPU acceleration. Since Arm GPUs are widely used in mobile and embedded devices, this vulnerability could affect a broad range of consumer and enterprise devices, potentially undermining trust in device security and leading to costly incident response and remediation efforts.
Mitigation Recommendations
1. Monitor Arm Ltd's official channels for patches addressing CVE-2024-4610 and apply them promptly once available. 2. Restrict local access to trusted users only, minimizing the risk of exploitation by unprivileged users. 3. Implement strict access controls and user privilege management on devices using affected GPU drivers. 4. Employ runtime security tools capable of detecting anomalous GPU memory operations or kernel driver misuse. 5. For enterprise environments, consider isolating critical systems or enforcing endpoint security policies that limit local code execution capabilities. 6. Conduct regular security audits focusing on kernel driver integrity and GPU-related processes. 7. Educate users and administrators about the risks of local access vulnerabilities and the importance of applying updates. 8. If possible, disable or limit GPU kernel driver features not required for normal operation until patches are applied. These steps go beyond generic advice by focusing on controlling local access vectors and monitoring GPU-specific behaviors.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Arm
- Date Reserved
- 2024-05-07T14:56:34.382Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 68f7d9b5247d717aace26b98
Added to database: 10/21/2025, 7:06:29 PM
Last enriched: 2/27/2026, 10:21:54 PM
Last updated: 3/21/2026, 9:10:57 PM
Views: 80
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.