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-2024-4610: CWE-416 Use After Free in Arm Ltd Bifrost GPU Kernel Driver

0
High
VulnerabilityCVE-2024-4610cvecve-2024-4610cwe-416
Published: Fri Jun 07 2024 (06/07/2024, 11:25:08 UTC)
Source: CVE Database V5
Vendor/Project: Arm Ltd
Product: 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

AILast updated: 10/21/2025, 19:26:45 UTC

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, enabling access to memory regions that have already been freed. This type of vulnerability can lead to arbitrary code execution, privilege escalation, or information disclosure by manipulating freed memory to execute malicious payloads or leak sensitive data. The vulnerability affects the kernel-mode GPU drivers responsible for managing GPU memory and operations on Arm architectures, which are widely used in embedded systems, mobile devices, and increasingly in edge computing environments. According to the CVSS v3.1 vector (AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), exploitation requires local access with high attack complexity but no privileges or user interaction, making it a significant threat in environments where local user access is possible. The vulnerability has not yet been observed exploited in the wild, and no patches have been publicly released at the time of reporting. However, the potential impact is severe due to the ability to compromise confidentiality, integrity, and availability of affected systems. This vulnerability underscores the need for careful management of GPU drivers and memory operations in kernel space, especially as GPUs become more integral to system operations beyond graphics, including AI and compute workloads.

Potential Impact

For European organizations, the impact of CVE-2024-4610 can be substantial, particularly in sectors relying on Arm-based embedded systems, such as telecommunications, automotive, industrial control systems, and IoT deployments. Successful exploitation could allow attackers to escalate privileges from a local user context to kernel-level control, enabling unauthorized access to sensitive data, manipulation of system operations, or denial of service via system crashes. This poses risks to data confidentiality, system integrity, and availability of critical infrastructure. Enterprises using Arm-based devices in secure environments may face increased risk of insider threats or lateral movement by attackers who gain local access. The vulnerability could also affect supply chain security if compromised devices are integrated into larger systems. Given the high confidentiality and integrity impact, organizations may face regulatory and compliance challenges under GDPR and other data protection laws if breaches occur. The lack of available patches necessitates immediate risk management and mitigation strategies to prevent exploitation.

Mitigation Recommendations

1. Restrict local user access to systems running affected Arm Bifrost and Valhall GPU drivers, enforcing strict access controls and user privilege separation. 2. Monitor system logs and GPU driver behavior for anomalies indicative of memory corruption or unauthorized GPU memory operations. 3. Employ host-based intrusion detection systems (HIDS) with capabilities to detect kernel-level anomalies. 4. Coordinate with Arm Ltd and device vendors to obtain and apply security patches or firmware updates as soon as they become available. 5. For critical environments, consider isolating or disabling GPU functionalities if feasible until patches are deployed. 6. Implement robust endpoint security policies that limit the installation of untrusted software and enforce application whitelisting. 7. Conduct regular security audits and penetration testing focusing on local privilege escalation vectors. 8. Educate system administrators and users about the risks of local access and the importance of maintaining updated systems. 9. For embedded and IoT devices, ensure secure boot and firmware integrity verification mechanisms are in place to prevent unauthorized modifications.

Need more detailed analysis?Get Pro

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: 10/21/2025, 7:26:45 PM

Last updated: 10/30/2025, 8:00:01 AM

Views: 11

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