Zero click, silent, remote Android DoS

323 points · 185 comments on HN · read original →

Points and comments are a snapshot, not live.

Malformed WAP Push SMS can remotely crash Android telephony, dropping all calls including emergency calls.

A single malformed WAP Push SMS exploits an unchecked cast in `WapPushOverSms.decodeWapPdu()`, causing a `NegativeArraySizeException` that crashes `com.android.phone`. The attack is zero-click, silent, and persistent: carrier redelivery re-crashes the device, and ~20 messages can render a phone unusable. Recovery requires ADB to delete queued messages from `content://sms/raw`. Google fixed this in the October 2026 security update for Android 14-17 by widening exception handling and deleting the triggering message. Australian regulations may force carriers to block phones that cannot reach emergency services, amplifying the impact.

What commenters are saying

Commenters criticized the practice of creating dedicated websites with logos for vulnerabilities, calling it overblown and linked to LLM-generated content. Some defended it as necessary when vendors mark issues as won't fix. A user noted this was already fixed in LineageOS and GrapheneOS previews, and Google assigned CVE-2026-58882 with Critical severity for the November 2026 bulletin, arguing Google mishandled the initial report. Others questioned whether carriers would actually forward such malformed SMS messages, with replies noting SS7's inherent trust model and the availability of cheap 4G modems to bypass carrier filters.