Coprocessor crash via out-of-bounds framebuffer write
Published Oct 24, 2024 · Updated Apr 2, 2026
An out-of-bounds write in IOMobileFrameBuffer in Apple macOS before 14.6 allows local users to crash a coprocessor through an app. IOMobileFrameBuffer insufficiently validates app-supplied input before a buffer write; Apple has not disclosed the affected function or input format. Reaching the flaw requires local low-privileged app execution, and the documented consequence is a coprocessor crash rather than code execution or data disclosure.
Summary
What happened
An out-of-bounds write in IOMobileFrameBuffer in Apple macOS before 14.6 allows local users to crash a coprocessor through an app. IOMobileFrameBuffer insufficiently validates app-supplied input before a buffer write; Apple has not disclosed the affected function or input format. Reaching the flaw requires local low-privileged app execution, and the documented consequence is a coprocessor crash rather than code execution or data disclosure.
The record
- CVE
- CVE-2024-40810
- Published
- Oct 24, 2024
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-787, T1499.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 24, 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 <14.6
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