← Voltar ao feed
high technology

GhostMap Android Flaw Can Cause Persistent Crash Loops on Devices Installing Malformed APKs

1 fonte(s) · 1 atualização(ões) · publicado 12/11/2026 04:33 · coletado há 1 hora

Researchers at Bitdefender Labs discovered GhostMap, a critical Android vulnerability affecting devices running Android 10 and later, including Pixel 10 on Android 17. This flaw exploits inconsistent handling by Android's libziparchive and libandroidfw libraries when parsing APK files compressed with ZIP format, leading to a SIGBUS error that crashes the system_server process. Affected devices can enter an unrecoverable crash loop upon installation of specially crafted apps without needing user interaction or app execution, potentially requiring a factory reset and causing local data loss. Attempts to recover via safe mode or restart fail; USB debugging affords limited recovery only if previously enabled. Google classified the issue as "Won't Fix (Not Reproducible)" initially but later referred it to a relevant team for potential inclusion in future Android versions .

Linha do tempo

  1. hackread.com ↗ · pub. 12/11/2026 04:33 · coletado 12/11 05:02 primeiro registro

    GhostMap Android Flaw Can Cause Persistent Crash Loops on Devices Installing Malformed APKs

    ler a análise desta fonte

    Researchers at Bitdefender Labs discovered GhostMap, a critical Android vulnerability affecting devices running Android 10 and later, including Pixel 10 on Android 17. This flaw exploits inconsistent handling by Android's libziparchive and libandroidfw libraries when parsing APK files compressed with ZIP format, leading to a SIGBUS error that crashes the system_server process. Affected devices can enter an unrecoverable crash loop upon installation of specially crafted apps without needing user interaction or app execution, potentially requiring a factory reset and causing local data loss. Attempts to recover via safe mode or restart fail; USB debugging affords limited recovery only if previously enabled. Google classified the issue as "Won't Fix (Not Reproducible)" initially but later referred it to a relevant team for potential inclusion in future Android versions .