Freed-memory access via improper GPU operations
Published Oct 3, 2023 · Updated Mar 7, 2025
Use-after-free in Arm Valhall r44p0 and 5th Gen GPU kernel drivers r41p0 through r44p0 allows local users to access freed memory. The driver accepts improper GPU processing operations that cross buffer bounds or trigger a software race after memory is carefully prepared; Arm has not named the affected function. A local nonprivileged process must reach the GPU driver, and successful exploitation is bounded to access to out-of-bounds or freed memory.
Summary
What happened
Use-after-free in Arm Valhall r44p0 and 5th Gen GPU kernel drivers r41p0 through r44p0 allows local users to access freed memory. The driver accepts improper GPU processing operations that cross buffer bounds or trigger a software race after memory is carefully prepared; Arm has not named the affected function. A local nonprivileged process must reach the GPU driver, and successful exploitation is bounded to access to out-of-bounds or freed memory.
The record
- CVE
- CVE-2023-34970
- Published
- Oct 3, 2023
- Updated
- Mar 7, 2025
- Vendor
- Arm
- Product
- Valhall GPU Kernel Driver
- Classifications
- CWE-416, CWE-787, CAPEC-233, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 3, 2023CVE publishedPublication date reported by the CVE source.
- Mar 7, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=r44p0 <r44p1 changes=[{"at":"r44p1","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo