Kernel code execution via GPU driver memory flaw
Published Sep 26, 2023 · Updated Nov 4, 2025
Memory-handling flaw in Apple iOS and iPadOS before 17 allows local users to execute arbitrary code with kernel privileges through GPU Drivers. Apple has not disclosed the GPU-driver operation or malformed input involved, stating only that improved memory handling addressed the issue. Exploitation requires a user to run an app on an affected iPhone or iPad and grants that app kernel-level code execution.
Summary
What happened
Memory-handling flaw in Apple iOS and iPadOS before 17 allows local users to execute arbitrary code with kernel privileges through GPU Drivers. Apple has not disclosed the GPU-driver operation or malformed input involved, stating only that improved memory handling addressed the issue. Exploitation requires a user to run an app on an affected iPhone or iPad and grants that app kernel-level code execution.
The record
- CVE
- CVE-2023-40431
- Published
- Sep 26, 2023
- Updated
- Nov 4, 2025
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- T1404
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 26, 2023CVE publishedPublication date reported by the CVE source.
- Nov 4, 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=unspecified <17
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