System hang via infinite GPU processing loop
Published Feb 3, 2025 · Updated Feb 3, 2025
An infinite loop in affected Arm Mali GPU Kernel Drivers allows local users to make the whole system unresponsive through valid GPU memory operations. Arm has not published the responsible function or explained why processing valid GPU memory operations enters an unreachable-exit loop. A non-privileged user process can reach the flaw directly or through WebGL or WebGPU, and successful exploitation hangs the entire host.
Summary
What happened
An infinite loop in affected Arm Mali GPU Kernel Drivers allows local users to make the whole system unresponsive through valid GPU memory operations. Arm has not published the responsible function or explained why processing valid GPU memory operations enters an unreachable-exit loop. A non-privileged user process can reach the flaw directly or through WebGL or WebGPU, and successful exploitation hangs the entire host.
The record
- CVE
- CVE-2024-6790
- Published
- Feb 3, 2025
- Updated
- Feb 3, 2025
- Vendor
- Arm
- Product
- Valhall GPU Kernel Driver
- Classifications
- CWE-835, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 3, 2025CVE publishedPublication date reported by the CVE source.
- Feb 3, 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=r44p1
- Affected versionversion=r46p0 <=r49p0 changes=[{"at":"r49p1","status":"unaffected"}]
- Affected versionversion=r50p0 <=r51p0 changes=[{"at":"r52p0","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