Kernel memory corruption through Pro Res
Published Oct 28, 2024 · Updated Apr 2, 2026
Memory corruption in Apple Pro Res allows local users to terminate the system or corrupt kernel memory through a malicious app. Apple identifies the affected locus as Pro Res but has not disclosed the specific memory operation or attacker-controlled input involved. Exploitation requires a locally installed app; the bounded outcomes are a system crash or kernel-memory corruption.
Summary
What happened
Memory corruption in Apple Pro Res allows local users to terminate the system or corrupt kernel memory through a malicious app. Apple identifies the affected locus as Pro Res but has not disclosed the specific memory operation or attacker-controlled input involved. Exploitation requires a locally installed app; the bounded outcomes are a system crash or kernel-memory corruption.
The record
- CVE
- CVE-2024-44277
- Published
- Oct 28, 2024
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-787, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 28, 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.1
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