Kernel code execution via undisclosed race condition
Published Nov 1, 2022 · Updated Apr 22, 2025
Kernel race condition in Apple macOS, tvOS, and watchOS allows local users to execute arbitrary code with kernel privileges. Apple identifies the locus only as the kernel and has not disclosed the competing operations, shared object, or affected routine behind the improper locking. An attacker-controlled local app and race timing are required; successful exploitation crosses the user-to-kernel boundary on macOS before 13, tvOS before 16.1, and watchOS before 9.1.
Summary
What happened
Kernel race condition in Apple macOS, tvOS, and watchOS allows local users to execute arbitrary code with kernel privileges. Apple identifies the locus only as the kernel and has not disclosed the competing operations, shared object, or affected routine behind the improper locking. An attacker-controlled local app and race timing are required; successful exploitation crosses the user-to-kernel boundary on macOS before 13, tvOS before 16.1, and watchOS before 9.1.
The record
- CVE
- CVE-2022-42803
- Published
- Nov 1, 2022
- Updated
- Apr 22, 2025
- Vendor
- Apple
- Product
- tvOS
- Classifications
- CWE-362, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 1, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 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 <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.
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