Google Cut Memory Tagging From the Pixel 11, and GrapheneOS Cannot Finish Its Port

Seven years. That is how long GrapheneOS shipped for Pixel phones and nothing else, because the Pixel was the only Android handset carrying the hardware the project needed. That run has ended, and it ended on Google's side.

GrapheneOS has a partial port running on the Pixel 11 and says it cannot finish it. The blocker is ARM Memory Tagging Extension, usually shortened to MTE.

What Pixel 11 memory tagging did, and why its absence matters

MTE stamps a small tag onto every memory allocation and checks that tag on every access. If the two do not match, the access fails immediately instead of quietly corrupting something else.

That matters because most serious exploits begin with a memory corruption bug: a use-after-free, a buffer overflow, something written where it should not have been. Those are the same primitives behind hypervisor escapes and most of the remote code execution entries that reach a patch bulletin. MTE catches a large share of that class at the hardware level, at the moment it happens, rather than leaving software to notice the damage afterwards.

The project says support is missing across software, firmware and near certainly the silicon itself. In plain terms, this is not a driver somebody can write later. GrapheneOS has said publicly that the feature appears to have been cut to save money.

The knock-on is already visible

Last week the project expanded support to more Motorola flagships, citing better Snapdragon hardware support and, pointedly, better MTE support. The Motorola Edge 60 Pro sits in that widening Snapdragon bracket and is available on Amazon.

Worth being careful with the tone here. Google has not confirmed a reason, and cost is the project's inference rather than a stated fact. A change of silicon supplier or a power budget decision would explain the same outcome. What is not in dispute is that the feature is gone, and that the most security-focused Android distribution in existence cannot ship for the newest Pixel.

What this means if you are buying a phone this year

The Pixel 10 still has MTE, and existing Pixel 9 and 10 hardware remains supported. If hardware memory tagging is part of why you buy a phone, check the specific handset before you order, because nobody advertises the absence of a feature. The full ordering of what actually helps is in our Android hardening checklist for 2026, and the wider pattern of patch-level decisions is visible in vendor bulletins like Oracle's 943-fix August batch.

The part worth sitting with is how this came to light. There was no announcement and no changelog entry. A volunteer project tried to compile against the hardware, the hardware did not answer, and that is how anyone found out.

Some links in this article are affiliate links. We may earn a small commission at no extra cost to you.