The previous post ended one function call short. Credentials, MACF (Mandatory Access Control Framework) labels and process state all moved into read-only zones, and the handful of allocator routines allowed to write them run in a privileged context. An arbitrary kernel write does not reach any of it. Calling one of those routines does, and calling something means getting an address you chose into a register the hardware is about to branch to.

That step used to be the cheap one. Find a pointer the target will call later, overwrite it, wait. Apple’s answer was not another check on the write. On arm64e, Apple’s pointer-authentication ABI, the pointer carries a cryptographic code in its own unused bits, the hardware verifies that code at the branch, and the key it verifies against is not in memory at all.