Freed GPU memory access via use-after-free
Published Dec 1, 2025 · Updated Dec 1, 2025
Use-after-free in Arm Valhall and 5th Gen GPU Kernel Drivers r53p0 through r54p1 allows local users to access freed GPU memory. Arm identifies improper GPU memory processing as the trigger but does not disclose the responsible function, request path, or lifetime error. A local non-privileged process must reach the GPU driver, and the documented impact is limited to reading or modifying data in the freed allocation.
Summary
What happened
Use-after-free in Arm Valhall and 5th Gen GPU Kernel Drivers r53p0 through r54p1 allows local users to access freed GPU memory. Arm identifies improper GPU memory processing as the trigger but does not disclose the responsible function, request path, or lifetime error. A local non-privileged process must reach the GPU driver, and the documented impact is limited to reading or modifying data in the freed allocation.
The record
- CVE
- CVE-2025-6349
- Published
- Dec 1, 2025
- Updated
- Dec 1, 2025
- Vendor
- Arm
- Product
- Valhall GPU Kernel Driver
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 1, 2025CVE publishedPublication date reported by the CVE source.
- Dec 1, 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=r53p0 <=r54p1 changes=[{"at":"r54p2","status":"unaffected"},{"at":"r55p0","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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