Kernel code execution via use-after-free
Published Sep 26, 2023 · Updated Nov 4, 2025
Use-after-free in the Apple kernel before iOS and iPadOS 17 or macOS 14 allows local users to execute code with kernel privileges. Kernel code accesses an object after its memory has been freed, but Apple has not published the affected routine or object type. Execution requires an attacker-controlled app to run, after which kernel-level code can compromise the operating system.
Summary
What happened
Use-after-free in the Apple kernel before iOS and iPadOS 17 or macOS 14 allows local users to execute code with kernel privileges. Kernel code accesses an object after its memory has been freed, but Apple has not published the affected routine or object type. Execution requires an attacker-controlled app to run, after which kernel-level code can compromise the operating system.
The record
- CVE
- CVE-2023-41995
- Published
- Sep 26, 2023
- Updated
- Nov 4, 2025
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 26, 2023CVE 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?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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