@GenericCoding I took screenshots of your Codex output and ran the timeline by my own diffing session. It found the A18 retype TLBI path was already present by iOS 26.5 beta 1, so 27.2 beta 2 wasn’t its first appearance.
@GenericCoding Verified static bound for the iPhone 15 Pro: the first checked restore image with issue-gmmu-tlbis-at-retype=1 is iOS 27.0 beta 2 (24A5370h). The SPTM property string appears by iOS 26.3, but the enabling DeviceTree key is absent through 26.5.2 and 27 beta 1.
@GenericCoding If you mean the SPTM TLBI issue, the earliest build we’ve verified with the pre-check path is my 15 Pro’s iOS 27.0.1 (24A446); beta 2 still has it, and beta 3 adds the check. That does not establish when the underlying bug first appeared tho
@GenericCoding Hi sorry no mic for right now, but I vibe questioned and worded it eloquently like johny was earlier and got "On iPhone 15 Pro/T8122 firmware , beta 3 adds a conditional handshake and GMMU verification check after the UAT range TLBI, before unmap state advances"
@GenericCoding the panic requires three gates the DeviceTree-enabled verifier, a UAT instance flag at +0x648, and a set bit in the configured status register after TLBI from my daybreak session
@GenericCoding WebKit is cursed. I’m trying to chain CVE’s together to get krw on 26.0 and I’m getting my ass kicked trying to get dyld interpose corruption
@GenericCoding Do you think they’ll make the mistake they did on 26.0 when the 17 pro released but on the duo ? I have a 17 pro on a weird 26.0 Build 23A330
Exploiting Reversing (ER) Series | Article 10: iOS Security Research (part 01)
223 pages, free. The first article in the series aimed at iOS itself, and the opening of a multi-part sequence.
Published on:
https://t.co/VlebcByqKG
This article will be published on https://t.co/GBDi0lO8Zd next week.
I would like to thank Ilfak Guilfanov (@ilfak) and Hex-Rays SA (@HexRaysSA) for the continuous support.
Hope you enjoy the read!
#iOS #Apple #VulnerabilityResearch #ExploitDevelopment #ReverseEngineering