Kernel code execution via corrupted state management
Published Nov 1, 2022 · Updated May 6, 2025
Kernel memory corruption in Apple macOS, tvOS, and watchOS allows local users to execute arbitrary code with kernel privileges. The kernel mishandles internal state in a way that corrupts memory; Apple has not disclosed the affected function or state transition. Execution requires a locally launched app and user interaction, after which code runs with kernel privileges and can fully compromise the device.
Summary
What happened
Kernel memory corruption in Apple macOS, tvOS, and watchOS allows local users to execute arbitrary code with kernel privileges. The kernel mishandles internal state in a way that corrupts memory; Apple has not disclosed the affected function or state transition. Execution requires a locally launched app and user interaction, after which code runs with kernel privileges and can fully compromise the device.
The record
- CVE
- CVE-2022-32944
- Published
- Nov 1, 2022
- Updated
- May 6, 2025
- Vendor
- Apple
- Product
- tvOS
- Classifications
- CWE-787, 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 <11.7
- Affected versionversion=unspecified <12.6
- 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.
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