Coprocessor memory corruption via improper bounds checks
Published Jan 16, 2026 · Updated Jan 16, 2026
Memory corruption in Apple iOS and iPadOS before 18.1 allows local users to corrupt coprocessor memory through a malicious app. The IOMobileFrameBuffer component fails to enforce buffer boundaries on app-controlled input before that input can alter coprocessor memory. The app requires low-privileged local execution, and Apple has not disclosed the affected request path or control beyond coprocessor memory.
Summary
What happened
Memory corruption in Apple iOS and iPadOS before 18.1 allows local users to corrupt coprocessor memory through a malicious app. The IOMobileFrameBuffer component fails to enforce buffer boundaries on app-controlled input before that input can alter coprocessor memory. The app requires low-privileged local execution, and Apple has not disclosed the affected request path or control beyond coprocessor memory.
The record
- CVE
- CVE-2024-44238
- Published
- Jan 16, 2026
- Updated
- Jan 16, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-119
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 16, 2026CVE publishedPublication date reported by the CVE source.
- Jan 16, 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=unspecified <18.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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