Kernel code execution via use-after-free
Published Jan 10, 2024 · Updated Nov 4, 2025
A kernel use-after-free in Apple iOS and iPadOS before 17 and macOS before 14 allows local users to execute code with kernel privileges. Apple has not published the affected kernel function or the operation that accesses the freed object. A malicious app must run locally; successful exploitation crosses the app boundary and gains kernel-level execution.
Summary
What happened
A kernel use-after-free in Apple iOS and iPadOS before 17 and macOS before 14 allows local users to execute code with kernel privileges. Apple has not published the affected kernel function or the operation that accesses the freed object. A malicious app must run locally; successful exploitation crosses the app boundary and gains kernel-level execution.
The record
- CVE
- CVE-2023-42870
- Published
- Jan 10, 2024
- Updated
- Nov 4, 2025
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 10, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 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 <17
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