Devy_Design

You should absolutely stay on 16.7.4/17.2.1 or lower. To be specific: Modern: - If you're already on 17.3 or 17.4b1, go to 17.2(.1) - If you're currently on 17.2.1 or earlier, STAY EoL: - If you're already on 16.7.5, go to 16.7.4 - If you're currently on 16.7.4 or earlier, STAY (To ensure I clarify again by the way, no, do not update in any way, shape, or form to 16.7.4/17.2(.1), you will be better of staying on your current version unless it is 16.7.5, 17.3, or 17.4b1) kernel r/w is a meaningful thing if it is achieved (huge emphasis on if - explained in the next section of this post) - here's what kernel r/w would likely allow for: - Jailed TS Installation on 16.7 RC and 17.0 - A semi-jailbreak on 16.7 RC and 17.0 - Potentially stuff like Misaka up to 16.7.4/17.2.1 - A full-fledged jailbreak up to 16.7.4/17.2 for A11 and earlier devices That being said, there are two integral things to note: - Somebody has to write an exploit for this vulnerability to be usable for something, please do not harass/bother/ask people to write one - all that will do is drive the people who are otherwise capable of doing so even further away from this community than they already have. - Depending on how similar this is to the kfd bugs (since kfd was a physical use-after-free - aka a puaf) this bug might be unexploitable on A15-A17 devices on 17.x due to SPTM - keep this in mind, as even if an exploit is developed, it may not be usable on SPTM devices. (For the record, even if an exploit isn't written for this bug, earlier will overall be better and have a higher chance of receiving an exploit than later versions) For those who are on 16.7.5, 17.3, or 17.4b1, here are the ipsw's: iOS 17.2.1: appledb.dev/firmware/iOS/21C… iPadOS 17.2: appledb.dev/firmware/iPadOS/… iOS 16.7.4: appledb.dev/firmware/iOS/20H… iPadOS 16.7.4: appledb.dev/firmware/iPadOS/…