Code execution via improper Kernel memory handling
Published May 13, 2024 · Updated Apr 2, 2026
A memory-handling flaw in the Kernel of Apple iOS and iPadOS before 17.5 and macOS Sonoma before 14.5 allows attackers to crash apps or execute code. Apple identifies improper Kernel memory handling but has not disclosed the faulty routine, object, or operation performed on untrusted input. An attacker must cause an application to reach the flaw, and NVD records local access plus user interaction; the bounded outcomes are app termination or code execution.
Summary
What happened
A memory-handling flaw in the Kernel of Apple iOS and iPadOS before 17.5 and macOS Sonoma before 14.5 allows attackers to crash apps or execute code. Apple identifies improper Kernel memory handling but has not disclosed the faulty routine, object, or operation performed on untrusted input. An attacker must cause an application to reach the flaw, and NVD records local access plus user interaction; the bounded outcomes are app termination or code execution.
The record
- CVE
- CVE-2024-27818
- Published
- May 13, 2024
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- iOS
- Classifications
- CWE-77, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 13, 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.5
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