GhostMap flaw lets a malicious Android app force a persistent boot loop
Affected devices can only be recovered by a factory reset or by deleting the file over ADB, a route that requires debugging to have been enabled beforehand.
Affected devices can only be recovered by a factory reset or by deleting the file over ADB, a route that requires debugging to have been enabled beforehand.
Updating is the main defence, since the exploited flaws are already fixed and a reboot ends activity on affected devices.
Phones on Android 14 through 17 need the security patch dated 2026-11-01 or later, and the second tranche must follow for kernel and chipset fixes.
Phones on Android 12 and 13 remain exposed, and some devices may need a factory reset after repeated attacks.
None were used in real attacks, and all were reported to vendors and patched, but outside readers cannot check how much of the work the model did alone.
Accepted stores will get one-tap installs and silent background updates, with rollout to some devices set for later this year.
Devices showing the wrong time after November 1 can be fixed through updates or manual time zone settings, and the same issue could reach the US if it adopts permanent daylight saving time.
Disabling the default leaves numbers already attached in place, so each account must be cleared by hand, and RCS chats fall back to SMS.
Thin staffing and little funding leave widely used code exposed to failures and security incidents across the software stack companies depend on.
An opt-in protection mode will scan unknown senders and links, while Google extends scam detection beyond Pixel to more Android devices.
Planned rules would formalise search-choice prompts, extend them to AI assistants, and tighten how publisher content is shown in results.
The ruling forces Google to fix how it handles location data in the EU within six months, tightening scrutiny of its data practices.