Kernel code execution via improper memory handling
Published Jan 23, 2024 · Updated Apr 2, 2026
Memory corruption in the Apple Kernel allows local users to execute arbitrary code with kernel privileges across four operating-system families. Apple states that improved memory handling resolves the issue but has not disclosed the faulty memory operation or attacker-controlled input. Affected releases are iOS and iPadOS before 17.3, macOS before 14.3, tvOS before 17.3, and watchOS before 10.3; execution of an app is required.
Summary
What happened
Memory corruption in the Apple Kernel allows local users to execute arbitrary code with kernel privileges across four operating-system families. Apple states that improved memory handling resolves the issue but has not disclosed the faulty memory operation or attacker-controlled input. Affected releases are iOS and iPadOS before 17.3, macOS before 14.3, tvOS before 17.3, and watchOS before 10.3; execution of an app is required.
The record
- CVE
- CVE-2024-23208
- Published
- Jan 23, 2024
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-94, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 23, 2024CVE publishedPublication date reported by the CVE source.
- Apr 2, 2026Record 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=0 <17.3
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