The article documents a zero-click-to-root exploit chain on Pixel 10: an updated Dolby decoder exploit (CVE-2025-54957) paired with a new VPU kernel driver flaw whose mmap handler maps unbounded physical memory, exposing the kernel image. The author credits Android's improved triage (High severity rating, 71-day fix) but argues the same vendor again shipped a shallow, easily found driver bug, so proactive driver security remains weak.
The author presents MAccConc, tooling that traces kernel memory accesses via ASAN outline instrumentation fed through KCOV, and uses count-augmented stack traces to stably identify accesses across runs, enabling delay injection that forces specific thread interleavings. This supports confirming race-condition candidates, writing reliable regression tests, and eventually fuzzing. Tradeoffs include ASAN missing some stack/global accesses, coverage loss on kernel panics, and constraint-style orderings being less deterministic than fully-specified ones; kernel patches are not yet upstream.
The article argues passkeys are technically strong—phishing-proof and breach-resistant—making them well-suited to enterprises, but a poor fit for individuals whose bigger risks are lockout, account bans, and device loss. It details pain points: hardware keys can't be backed up and have per-key credential limits, platform-synced passkeys tie you to Apple/Google accounts, export/interoperability is immature, and cross-device login is clunky. It recommends passwords in a third-party manager plus a separate TOTP app, except for habitual password reusers.