Freed-memory access via improper GPU operations
Published Nov 7, 2023 · Updated Dec 16, 2025
Use-after-free in Arm Valhall GPU Kernel Driver r38p0 through r44p0 allows local users to access freed memory via crafted GPU operations. The driver processes carefully prepared GPU memory operations after an allocation's lifetime has ended, although Arm has not identified the affected function. Local non-privileged access to the GPU device is required, and the demonstrated consequence is access to memory that the driver already freed.
Summary
What happened
Use-after-free in Arm Valhall GPU Kernel Driver r38p0 through r44p0 allows local users to access freed memory via crafted GPU operations. The driver processes carefully prepared GPU memory operations after an allocation's lifetime has ended, although Arm has not identified the affected function. Local non-privileged access to the GPU device is required, and the demonstrated consequence is access to memory that the driver already freed.
The record
- CVE
- CVE-2023-3889
- Published
- Nov 7, 2023
- Updated
- Dec 16, 2025
- Vendor
- Arm
- Product
- Valhall GPU Kernel Driver
- Classifications
- CWE-119, CWE-667, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 7, 2023CVE publishedPublication date reported by the CVE source.
- Dec 16, 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=r38p0 <=r44p0 changes=[{"at":"r44p1","status":"unaffected"},{"at":"r45p0","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