Kernel code execution via insufficient bounds checks
Published Nov 1, 2022 · Updated May 6, 2025
Bounds-checking failure in the Apple kernel in tvOS before 16.1, macOS before 13, and watchOS before 9.1 allows local users to execute kernel code. The kernel performs insufficient bounds checks during an undisclosed operation; Apple has not identified the affected function or input path. Exploitation requires an app already running with root privileges, and success crosses the remaining boundary into kernel-privileged arbitrary code execution.
Summary
What happened
Bounds-checking failure in the Apple kernel in tvOS before 16.1, macOS before 13, and watchOS before 9.1 allows local users to execute kernel code. The kernel performs insufficient bounds checks during an undisclosed operation; Apple has not identified the affected function or input path. Exploitation requires an app already running with root privileges, and success crosses the remaining boundary into kernel-privileged arbitrary code execution.
The record
- CVE
- CVE-2022-32926
- Published
- Nov 1, 2022
- Updated
- May 6, 2025
- Vendor
- Apple
- Product
- tvOS
- Classifications
- CWE-119, T1068
- Attack vector
- local
- Privileges
- admin
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