Kernel code execution via undisclosed validation flaw
Published Jan 27, 2025 · Updated Jun 2, 2026
Kernel validation failure in affected Apple operating systems allows local users to execute arbitrary code with kernel privileges through an app. The Kernel component applies insufficient validation in an undisclosed code path; Apple identifies only that improved logic corrects the operation. Execution of an app on the target is required, and successful exploitation grants that app kernel-level code execution across affected devices.
Summary
What happened
Kernel validation failure in affected Apple operating systems allows local users to execute arbitrary code with kernel privileges through an app. The Kernel component applies insufficient validation in an undisclosed code path; Apple identifies only that improved logic corrects the operation. Execution of an app on the target is required, and successful exploitation grants that app kernel-level code execution across affected devices.
The record
- CVE
- CVE-2025-24159
- Published
- Jan 27, 2025
- Updated
- Jun 2, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-94, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 27, 2025CVE publishedPublication date reported by the CVE source.
- Jun 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 <18.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