GrapheneOS says it cannot finish a Pixel 11 port because ARM memory tagging is missing

Sources: primary, releases, discussion
Summary: A post from the GrapheneOS account on Bluesky, verified by the grapheneos.org domain handle, states the project cannot finish a Pixel 11 port because ARM memory tagging support is absent, in software and firmware and, on the project's own hedge, near certainly in hardware. grapheneos.org/releases lists supported devices only through the Pixel 10 series and Pixel 10a, at build 2026081300, which corroborates that no Pixel 11 build exists, and that page says nothing about memory tagging. The project attributes the removal to a cost decision by Google, which is its inference rather than an established fact, and Google has published nothing on the subject that this run could read.
Why it matters: ARM memory tagging turns use-after-free and buffer-overflow bugs into faults rather than exploitable conditions, and the Pixel line has been its main consumer-device vehicle, so its absence removes the hardware backing under the hardened allocator GrapheneOS builds on.
Follow-up: Track whether Google states a position on memory tagging in the Pixel 11, and whether a Pixel 11 build appears on grapheneos.org/releases.