Local memory corruption via improper GPU operations
Published Feb 5, 2024 · Updated May 15, 2025
Out-of-bounds write in Arm Mali GPU Kernel Drivers r41p0 through r45p0 allows local users to corrupt memory via improper GPU operations. Arm has not published the affected function or buffer; the disclosed operation writes beyond buffer bounds during GPU memory processing. Reachability depends on the driver configuration and carefully prepared system memory, and the bounded consequence is corruption of memory outside the intended buffer.
Summary
What happened
Out-of-bounds write in Arm Mali GPU Kernel Drivers r41p0 through r45p0 allows local users to corrupt memory via improper GPU operations. Arm has not published the affected function or buffer; the disclosed operation writes beyond buffer bounds during GPU memory processing. Reachability depends on the driver configuration and carefully prepared system memory, and the bounded consequence is corruption of memory outside the intended buffer.
The record
- CVE
- CVE-2023-5643
- Published
- Feb 5, 2024
- Updated
- May 15, 2025
- Vendor
- Arm
- Product
- Valhall GPU Kernel Driver
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 5, 2024CVE publishedPublication date reported by the CVE source.
- May 15, 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=r41p0 <=r45p0 changes=[{"at":"r46p0","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.
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