Back to the notes

GrapheneOS might skip the Pixel 11 because Google dropped a security chip

The most secure Android ROM just said it might not support Google's next flagship phone. The reason is a missing hardware component that makes remote attestation work.

Processor Technology SOL 20 Computer
Swtpc6800 en:User:Swtpc6800 Michael Holley / Wikimedia Commons. Resized and converted to WebP. Public domain

GrapheneOS announced they might skip supporting the Pixel 11 because Google appears to have removed the StrongBox keymaster from the device. That is the dedicated security chip that handles cryptographic operations in isolated hardware. The Pixel 10 has it. The Pixel 9 has it. The Pixel 11 does not, at least not in the current engineering samples GrapheneOS developers have seen. This matters because StrongBox is how you prove to a remote server that a key was generated inside secure hardware and has never left it. Without that chip, key attestation falls back to the Trusted Execution Environment in the main processor. That is still isolated from Android, but it shares silicon with everything else. The attack surface is larger. GrapheneOS built their entire identity verification system on hardware attestation. Their app checks that you are running genuine GrapheneOS on a real Pixel with an unlocked bootloader and unmodified system partitions. All of that relies on StrongBox being present and correctly implemented. If the Pixel 11 ships without StrongBox, GrapheneOS either rewrites their attestation system to accept weaker guarantees or they skip the device entirely. They are leaning towards skipping it. Google has not confirmed this publicly. The Pixel 11 is not announced yet. But GrapheneOS is usually working from leaked specs or early hardware months before launch, and they have been right about this sort of thing before. The strange part is why Google would remove it. StrongBox has been standard on flagship Pixels since the Pixel 3. Removing it saves maybe two dollars per phone and makes every security-focused use case slightly worse. Either Google sees attestation as low-value or they are planning to replace StrongBox with something else in the Tensor G6 chip. Either way, the most hardened Android distribution just told its users they might need to stay on last year’s phone. That is not a normal product cycle problem.


Source: Pixel 11 doesn’t yet meet the GrapheneOS security standards and may be skipped

Back to all notes

Behind the notes

Vikrant
Sharma.

Artificial Intelligence Engineer intern at Voxon Photonics in Adelaide. Studying a Master of Information and Communications Technology at UniSC, with a focus on data, machine learning and security.

Meet the person behind the work