System crash or kernel-memory write via application
Published Jan 27, 2025 · Updated Jun 2, 2026
Kernel memory corruption in macOS before 14.7.3 or 15.3 and iPadOS before 17.7.4 allows local users to crash systems. The Kernel component mishandles memory during an undisclosed operation, allowing an application either to terminate the system unexpectedly or write kernel memory. Execution of an application on an affected device is required; Apple has not disclosed the malformed input, vulnerable function, or whether kernel-memory writes enable code execution.
Summary
What happened
Kernel memory corruption in macOS before 14.7.3 or 15.3 and iPadOS before 17.7.4 allows local users to crash systems. The Kernel component mishandles memory during an undisclosed operation, allowing an application either to terminate the system unexpectedly or write kernel memory. Execution of an application on an affected device is required; Apple has not disclosed the malformed input, vulnerable function, or whether kernel-memory writes enable code execution.
The record
- CVE
- CVE-2025-24118
- Published
- Jan 27, 2025
- Updated
- Jun 2, 2026
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-787, T1203
- 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 <14.7.3
- Affected versionversion=0 <15.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.
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