Kernel code execution via out-of-bounds write
Published Sep 20, 2022 · Updated May 29, 2025
Kernel memory corruption in Apple iOS before 16 and macOS before 11.7 or 12.6 allows local users to execute code with kernel privileges. The Kernel component performs an out-of-bounds write while handling app-controlled data, but Apple has not disclosed the affected routine or data structure. A locally running app with low privileges can cross the kernel boundary and gain complete control of the device.
Summary
What happened
Kernel memory corruption in Apple iOS before 16 and macOS before 11.7 or 12.6 allows local users to execute code with kernel privileges. The Kernel component performs an out-of-bounds write while handling app-controlled data, but Apple has not disclosed the affected routine or data structure. A locally running app with low privileges can cross the kernel boundary and gain complete control of the device.
The record
- CVE
- CVE-2022-32911
- Published
- Sep 20, 2022
- Updated
- May 29, 2025
- Vendor
- Apple
- Product
- iOS
- Classifications
- CWE-787, T1404, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 20, 2022CVE publishedPublication date reported by the CVE source.
- May 29, 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