System crash or kernel memory corruption
Published Mar 10, 2025 · Updated Apr 2, 2026
Memory corruption in Apple iOS and iPadOS before 18 and macOS before 15 allows attackers to crash the system or corrupt kernel memory. Apple identifies the Wi-Fi component and improved memory handling, but has not disclosed the faulty operation or attacker-controlled input. Exploitation requires an app to execute on the device; the documented consequences are system termination and kernel-memory corruption, with no published claim of code execution.
Summary
What happened
Memory corruption in Apple iOS and iPadOS before 18 and macOS before 15 allows attackers to crash the system or corrupt kernel memory. Apple identifies the Wi-Fi component and improved memory handling, but has not disclosed the faulty operation or attacker-controlled input. Exploitation requires an app to execute on the device; the documented consequences are system termination and kernel-memory corruption, with no published claim of code execution.
The record
- CVE
- CVE-2024-44227
- Published
- Mar 10, 2025
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-400, T1499.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Mar 10, 2025CVE 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 <18
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.
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