Kernel memory corruption via out-of-bounds write
Published Dec 11, 2024 · Updated Apr 2, 2026
An out-of-bounds write in the Kernel component of Apple operating systems allows local users to corrupt kernel memory or terminate the system. Apple has not disclosed the precise kernel routine, input, or incorrect memory operation beyond stating that memory handling was improved. Exploitation requires user interaction to run an app locally; no confidentiality impact is reported, and triggering the flaw can crash the device or compromise kernel-memory integrity.
Summary
What happened
An out-of-bounds write in the Kernel component of Apple operating systems allows local users to corrupt kernel memory or terminate the system. Apple has not disclosed the precise kernel routine, input, or incorrect memory operation beyond stating that memory handling was improved. Exploitation requires user interaction to run an app locally; no confidentiality impact is reported, and triggering the flaw can crash the device or compromise kernel-memory integrity.
The record
- CVE
- CVE-2024-44245
- Published
- Dec 11, 2024
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-787, T1204
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 11, 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 <18.2
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