Coprocessor memory corruption via unchecked bounds
Published Jan 27, 2025 · Updated Apr 2, 2026
Out-of-bounds write in Apple iOS, iPadOS, macOS, tvOS, and watchOS allows local users to corrupt coprocessor memory. IOMobileFrameBuffer performs insufficient bounds checking before writing to coprocessor memory, permitting an installed app to write beyond the intended region. Local app execution with ordinary user privileges is required; published evidence establishes memory corruption but does not identify code execution or persistent device compromise.
Summary
What happened
Out-of-bounds write in Apple iOS, iPadOS, macOS, tvOS, and watchOS allows local users to corrupt coprocessor memory. IOMobileFrameBuffer performs insufficient bounds checking before writing to coprocessor memory, permitting an installed app to write beyond the intended region. Local app execution with ordinary user privileges is required; published evidence establishes memory corruption but does not identify code execution or persistent device compromise.
The record
- CVE
- CVE-2024-54517
- Published
- Jan 27, 2025
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 27, 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.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.
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