GoKawiilJoe Maring / Android Authority
Add Android Authority on Google: Preferred Source Google Discover
TL;DR GrapheneOS found MTE hardware support in the Pixel 11 after earlier concerns.
The discovery could keep GrapheneOS support alive for Google’s latest phones.
Developers are testing MTE performance before deciding whether support for Pixel 11 is viable.
GrapheneOS appeared ready to walk away from the Pixel 11 series just a few days ago. The privacy-focused Android project even warned against buying the phones after discovering they lacked hardware support for Memory Tagging Extension (MTE), a key security feature. But that warning may have been premature: GrapheneOS developers have now found that Pixel 11 phones do have MTE hardware support, giving the project a potential path toward supporting Google’s latest flagships.
GrapheneOS shared the news on X, and they made this discovery after Google released Android 17 QPR2 Beta 4, the first beta version to support the Pixel 11 series. Developers examining the new firmware found references indicating the phones have the necessary MTE capability, despite earlier software suggesting otherwise.
That’s potentially good news for Pixel 11 owners interested in running GrapheneOS. MTE adds another layer of protection against memory-related flaws by using hardware tags to identify when software accesses memory incorrectly. Bugs such as buffer overflows and use-after-free vulnerabilities can otherwise provide attackers with opportunities to compromise devices.
GrapheneOS had previously warned that the apparent absence of MTE could make the Pixel 11 incompatible with its security standards. Still, the latest finding doesn’t guarantee support. GrapheneOS describes the Pixel 11’s MTE capability as only “bare minimum” and is still investigating whether the implementation is good enough for its needs.
The project developers also believe Google may have compromised MTE performance by removing much of its CPU-cache acceleration, potentially as a cost-saving measure. If so, switching the protection back on could impose a noticeable performance hit. That may help explain why Google left MTE turned off despite the underlying hardware supporting it.
... continue reading