Cross-process memory access via GPU use-after-free
Published May 3, 2024 · Updated Mar 27, 2025
Use-after-free in Arm Mali GPU kernel drivers r41p0 through r47p0 allows local users to affect another process's memory. Arm has not disclosed the precise allocation and freeing locus; crafted GPU memory operations reuse freed storage under affected driver configurations. Exposure requires an Armv8.0 core and a susceptible Linux kernel and Mali driver combination, enabling cross-process memory effects.
Summary
What happened
Use-after-free in Arm Mali GPU kernel drivers r41p0 through r47p0 allows local users to affect another process's memory. Arm has not disclosed the precise allocation and freeing locus; crafted GPU memory operations reuse freed storage under affected driver configurations. Exposure requires an Armv8.0 core and a susceptible Linux kernel and Mali driver combination, enabling cross-process memory effects.
The record
- CVE
- CVE-2024-1067
- Published
- May 3, 2024
- Updated
- Mar 27, 2025
- Vendor
- Arm
- Product
- Valhall GPU Kernel Driver
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 3, 2024CVE publishedPublication date reported by the CVE source.
- Mar 27, 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 <=r47p0 changes=[{"at":"r48p0","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