Kernel code execution via Graphics Driver memory corruption
Published Dec 15, 2022 · Updated Apr 21, 2025
Memory corruption in the Graphics Driver in Apple iOS and iPadOS before 16.2 allows local users to execute code with kernel privileges. The driver mishandles memory while processing app-controlled data, but Apple has not disclosed the exact object, operation, or memory-safety failure. Execution requires a user to run a crafted app, after which attacker-controlled code operates in the kernel and can compromise the device.
Summary
What happened
Memory corruption in the Graphics Driver in Apple iOS and iPadOS before 16.2 allows local users to execute code with kernel privileges. The driver mishandles memory while processing app-controlled data, but Apple has not disclosed the exact object, operation, or memory-safety failure. Execution requires a user to run a crafted app, after which attacker-controlled code operates in the kernel and can compromise the device.
The record
- CVE
- CVE-2022-42850
- Published
- Dec 15, 2022
- Updated
- Apr 21, 2025
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-787, T1404
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 15, 2022CVE publishedPublication date reported by the CVE source.
- Apr 21, 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 <16.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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