Kernel code execution via insufficient graphics bounds checks
Published Nov 1, 2022 · Updated May 6, 2025
Out-of-bounds access in Apple iOS and iPadOS Graphics Driver before 15.7.1 and in iOS 16.0 allows local users to execute kernel code. Apple identifies the locus only as Graphics Driver and says improved bounds checks corrected the issue; the affected operation and input format remain undisclosed. A local app and user interaction are required; successful exploitation executes attacker-controlled code with kernel privileges.
Summary
What happened
Out-of-bounds access in Apple iOS and iPadOS Graphics Driver before 15.7.1 and in iOS 16.0 allows local users to execute kernel code. Apple identifies the locus only as Graphics Driver and says improved bounds checks corrected the issue; the affected operation and input format remain undisclosed. A local app and user interaction are required; successful exploitation executes attacker-controlled code with kernel privileges.
The record
- CVE
- CVE-2022-32939
- Published
- Nov 1, 2022
- Updated
- May 6, 2025
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-119, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 1, 2022CVE publishedPublication date reported by the CVE source.
- May 6, 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 <15.7
- Affected versionversion=unspecified <16.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