System termination via improper GPU memory initialization
Published Jan 15, 2025 · Updated Apr 2, 2026
Memory initialization flaw in Apple GPU Drivers on affected iOS, iPadOS, and macOS releases allows local apps to terminate the system. Apple discloses only that GPU Drivers handle initialized memory improperly; no lower-level code locus or triggering input is public. Execution of an app on the device is required, and the documented consequence is unexpected system termination without disclosed data exposure or code execution.
Summary
What happened
Memory initialization flaw in Apple GPU Drivers on affected iOS, iPadOS, and macOS releases allows local apps to terminate the system. Apple discloses only that GPU Drivers handle initialized memory improperly; no lower-level code locus or triggering input is public. Execution of an app on the device is required, and the documented consequence is unexpected system termination without disclosed data exposure or code execution.
The record
- CVE
- CVE-2024-40854
- Published
- Jan 15, 2025
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- T1529
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 15, 2025CVE publishedPublication date reported by the CVE source.
- Apr 2, 2026Record 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=0 <17.7.1
- Affected versionversion=0 <18.1
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