A day^W^W Several months in the life of Project Zero - Part 1: The Chrome bug of suffering

Summary: Google Project Zero researchers Sergei Glazunov and Mark Brand describe a Chrome for Android heap-buffer-overflow that ClusterFuzz caught with a two-line test-case loading example.com and example.net, then stopped reproducing. The ASAN trace showed a write of 3848 bytes into a 1-byte IOBuffer in net::SpdyReadQueue::Dequeue, and the team traced a likely cause to HttpCache::Transaction::WriteResponseInfoToEntry setting io_buf_len_ from a PickledIOBuffer while read_buf_ still pointed at the old buffer.
Bottom line: The bug sat in the network service, which Chrome had split into its own process but not yet fully sandboxed, so on the researchers' reading this single flaw was enough for both initial code execution and sandbox escape on Android.

Read the original at Google Project Zero ↗

Topics: Vulnerabilities & Patching
Related: Attackers Exploit UnrealIRCd Flaw That Enables Server-Level Command Injection Cyber Risks · Nov 14, 2026
U.S. CISA adds Check Point and UnrealIRCd flaws to its Known Exploited Vulnerabilities catalog Cyber Risks · Nov 14, 2026
PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE Cyber Risks · Nov 13, 2026