Kernel code execution via undisclosed memory mishandling
Published Nov 1, 2022 · Updated May 5, 2025
Memory corruption in Apple Neural Engine in Apple iOS before 16 and watchOS before 9 allows context-dependent attackers to execute kernel code. Apple identifies only deficient memory handling in the Apple Neural Engine and has not disclosed the faulty operation or input path. Execution of a malicious app is required, after which attacker-controlled code runs with kernel privileges and can fully compromise the device.
Summary
What happened
Memory corruption in Apple Neural Engine in Apple iOS before 16 and watchOS before 9 allows context-dependent attackers to execute kernel code. Apple identifies only deficient memory handling in the Apple Neural Engine and has not disclosed the faulty operation or input path. Execution of a malicious app is required, after which attacker-controlled code runs with kernel privileges and can fully compromise the device.
The record
- CVE
- CVE-2022-32889
- Published
- Nov 1, 2022
- Updated
- May 5, 2025
- Vendor
- Apple
- Product
- iOS
- Classifications
- T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 1, 2022CVE publishedPublication date reported by the CVE source.
- May 5, 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
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