A forgotten safety check in the core of iOS
According to Apple, an app could use it to crash the device or corrupt kernel memory, the most protected part of the system.
While comparing iOS builds, I noticed that a new operation in IOMobileFrameBuffer lacked a condition present in a related one. That difference became an out-of-bounds hypothesis, a proof of concept, and a report to Apple.
Technical summary
From difference to hypothesis
I used binary diffing to narrow down security-relevant changes during the iOS beta cycle. Comparing related operations helped isolate a missing condition and formulate a testable out-of-bounds hypothesis.
Test, then report
I developed an on-device proof of concept and documented the result for Apple. I directed the investigation and used AI to accelerate reverse analysis, PoC development, and the technical report.
Public outcome
Apple credited the issue as CVE-2026-65398, with shared attribution. Its advisory describes an out-of-bounds access issue that could allow an app to cause a system crash or corrupt kernel memory.
