Freed-memory disclosure via improper GPU operations
Published Jan 8, 2024 · Updated May 22, 2025
Use-after-free in Arm Valhall GPU Kernel Driver r37p0 through r40p0 allows local users to access previously freed memory. Arm has not published the affected function or the GPU processing sequence that dereferences the freed allocation. A non-privileged local account with access to the GPU interface is required; disclosed impact is access to freed memory.
Summary
What happened
Use-after-free in Arm Valhall GPU Kernel Driver r37p0 through r40p0 allows local users to access previously freed memory. Arm has not published the affected function or the GPU processing sequence that dereferences the freed allocation. A non-privileged local account with access to the GPU interface is required; disclosed impact is access to freed memory.
The record
- CVE
- CVE-2023-5091
- Published
- Jan 8, 2024
- Updated
- May 22, 2025
- Vendor
- Arm
- Product
- Valhall GPU Kernel Driver
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 8, 2024CVE publishedPublication date reported by the CVE source.
- May 22, 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=r37p0 <=r40p0 changes=[{"at":"r41p0","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