tiktag

ARM/IoT community: https://community.arm.com/support-forums/f/architectures-and... https://community.arm.com/arm-community-blogs/b/internet-of-... Security practitioners and academics: https://github.com/enovella/TEE-reversing/ https://media.ccc.de/v/36c3-10859-trustzone-m_eh_breaking_ar... https://www.blackhat.com/docs/us-15/materials/us-15-Shen-Att... https://i.blackhat.com/USA-19/Thursday/us-19-Peterlin-Breaki... Sorry you could not cite an attack demonstrated on x86 and not on ARM or vice versa. Well, maybe TikTag (https://github.com/compsec-snu/tiktag) was demonstrated against ARM MTE, since you mention, and Pacman (https://pacmanattack.com/) against PAC. I was hoping for an actual response, no offense.

ARM has confirmed the possibility of an attack on systems with Cortex-X2, Cortex-X3, Cortex-A510, Cortex-A520, Cortex-A710, Cortex-A715 and Cortex-A720 processors, but does not intend to make changes to the CPU to block the problem[0], as how the MemTag architecture means that tags are not sensitive data to applications. Chrome's security team acknowledged the issues but won't fix them, as the V8 sandbox isn't designed for memory data confidentiality, and MTE defenses aren't enabled by default. It's mentioned quite early in the paper but there's a prototype toolkit on GitHub[1] if you want to jump straight into that. [0]: https://developer.arm.com/documentation/109544/latest [1]: https://github.com/compsec-snu/tiktag