Freed kernel-memory access via software race
Published Feb 5, 2024 · Updated Aug 2, 2024
Use-after-free in Arm Bifrost and Valhall GPU Kernel Drivers r35p0 through r40p0 allows local users to access freed kernel memory. The drivers process GPU memory during a software race after the user carefully prepares system memory, leaving a freed allocation reachable. Local non-privileged access is required; Arm has not published the affected function, and consequences beyond freed-memory access remain undisclosed.
Summary
What happened
Use-after-free in Arm Bifrost and Valhall GPU Kernel Drivers r35p0 through r40p0 allows local users to access freed kernel memory. The drivers process GPU memory during a software race after the user carefully prepares system memory, leaving a freed allocation reachable. Local non-privileged access is required; Arm has not published the affected function, and consequences beyond freed-memory access remain undisclosed.
The record
- CVE
- CVE-2023-5249
- Published
- Feb 5, 2024
- Updated
- Aug 2, 2024
- Vendor
- Arm
- Product
- Valhall GPU Kernel Driver
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 5, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record 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=r35p0 <=r40p0
- Affected versionversion=r35p0 <=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.
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