Android OS privilege escalation flaws under exploitation
Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
Multiple Android privilege escalation vulnerabilities, including CVE-2024-53104 under active exploitation, affect devices prior to February 2025 patch.
Google has released fixes for multiple privilege escalation vulnerabilities across Android OS components including Framework, Platform, System, and Kernel affecting all Android devices not yet patched to the 2025-02-05 security level or later. The most critical vulnerabilities are in the Framework (CVE-2024-49721, CVE-2024-49743, CVE-2024-49746, CVE-2025-0097, CVE-2025-0098, CVE-2025-0099), Platform (CVE-2025-0094), System (CVE-2025-0091, CVE-2025-0095, CVE-2025-0096), and Kernel (CVE-2024-53104, CVE-2025-0088) components. Successful exploitation grants an attacker elevated privileges within the affected component context, potentially enabling malicious application installation, data manipulation, or creation of privileged accounts.
Critically, CVE-2024-53104, a Kernel vulnerability, shows evidence of limited, targeted exploitation in the wild. The advisory also documents lower-severity information disclosure and denial-of-service vulnerabilities affecting Framework and System components, plus additional issues in third-party components from ARM, Imagination Technologies, MediaTek, Unisoc, and Qualcomm. Defenders should prioritize patching to the February 5, 2025 security level or later on all Android devices, implement automated patch management, and enable anti-exploitation protections where available.
Mentioned in this report
Source reporting: https://www.cisecurity.org/advisory/multiple-vulnerabilities-in-google-android-os-could-allow-for-privilege-escalation_2025-013
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 13,853 reports from 146 sources, 616 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs