Loading story…
GrapheneOS warned users not to buy Google's Pixel 11 for its hardened Android distribution and said it may abandon its incomplete Android 17 port after finding no ARM Memory Tagging Extension (MTE) support in the device's software or firmware. The project believes MTE is also likely absent from the hardware; the feature uses tagged memory allocations to detect invalid accesses and materially complicate exploitation of memory-corruption flaws, including remote and local attacks.
GrapheneOS has used MTE extensively across its base OS, kernel, and standard system processes since the Pixel 8, and considers its removal a significant security regression. While Pixel 11 reportedly adds ML-DSA post-quantum verified boot, AOSP IMS, and improved Titan M3 protections before first unlock, GrapheneOS said these controls do not compensate for missing MTE. It recommends Pixel 8, Pixel 9, or Pixel 10 models for GrapheneOS deployments and may place greater emphasis on future Motorola devices through its partnership.
See affected versions and whether adversaries are exploiting it.
4 events from the most recent confirmed update back to the earliest known activity.
GrapheneOS-reported observations indicated that Android 17 QPR2 Beta 4 added Pixel 11 support and firmware changes restoring some MTE support. The reported restoration, its performance implications, and any related hardware or firmware limitations had not been independently confirmed.
GrapheneOS said it may abandon Pixel 11 support and advised prospective GrapheneOS users not to buy the device, or to return it if possible. The project recommended Pixel 8, 9, and 10 models instead, stating Pixel 11's other reported protections do not offset the loss of MTE.
During a partial Android 17-based port to the Pixel 11, GrapheneOS found ARM Memory Tagging Extension support absent from software and firmware and likely unavailable in hardware. It said this prevents completion of the port because MTE underpins protections in its OS, kernel, and standard processes.
GrapheneOS and Motorola announced a partnership to produce high-end Qualcomm-based smartphones, which GrapheneOS expects will provide direct access to components for secure Google-free Android devices.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
3 references tracked. Mallory keeps watching after this page renders.
thecybersecguru.com
Open sourcescworld.com
Open sourceheise.de
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Google Project Zero reported that the first handset with **ARM Memory Tagging Extension (MTE)** reached the market, marking a notable deployment of hardware-backed memory-safety defenses aimed at detecting classes of memory corruption such as use-after-free and out-of-bounds access. The rollout followed Project Zero's earlier implementation testing of MTE, which examined how the feature behaves in practice and highlighted its potential to harden user-space software against exploitation techniques long used in browser and sandbox escapes. Subsequent analysis of MTE in major heap allocators found that the protection materially improves heap-corruption mitigation but leaves important differences in coverage and bypass resistance. Research comparing Chrome's **PartitionAlloc**, **glibc ptmalloc**, and Android's **Scudo** said allocator design choices affect tag randomization, chunk-size coverage, and performance, and noted a previously reported weakness in PartitionAlloc's deterministic tag increment and tag reuse that could let a use-after-free attacker cycle tags to evade checks under some conditions. The findings also said MTE does not fully solve uninitialized memory, stack safety, large shared-buffer protection, or all `mmap`-backed allocation cases, underscoring that the new handset support is a meaningful but incomplete step in reducing memory-corruption risk.
Aug 24, 2026
A technical review details the internal mechanisms of GrapheneOS's hardened malloc, a security-focused memory allocator designed to mitigate memory corruption vulnerabilities. Key features include integration of ARM Memory Tagging Extension (MTE), double quarantine for use-after-free protection, randomized guard pages, and strict metadata isolation. These mechanisms significantly raise the bar for exploitation on GrapheneOS devices compared to standard Android implementations.
Jun 29, 2026
Motorola confirmed a long-term partnership with the **GrapheneOS Foundation** to enable future Motorola smartphones to support (and potentially ship with) the privacy- and security-hardened Android-derived OS, with early compatibility/signals pointing to **2027** availability. Reporting tied the announcement to Mobile World Congress and noted this would be GrapheneOS’s first official expansion beyond its historical **Google Pixel-only** support model, which was driven by strict device security and update requirements; current Motorola flagships reportedly do not yet meet GrapheneOS hardware/security prerequisites, implying initial support may target premium devices. GrapheneOS is positioned as a hardened AOSP-based platform with security features such as stronger app sandboxing and granular controls (e.g., network/sensor access), and it can run many Google Play apps while also offering components like the *Vanadium* browser and a GrapheneOS app store. Motorola also indicated it may bring select GrapheneOS “features/concepts” into its broader Android experience separate from full GrapheneOS devices; commentary also flagged potential customer concerns about Motorola’s ownership structure (Lenovo) in the context of privacy expectations.
Jun 29, 2026