Multiple Vulnerabilities in Google Android OS Could Allow for Privilege Escalation

Multiple vulnerabilities have been discovered in Google Android OS, the most severe of which could allow for privilege escalation. Android is an operating system developed by Google for mobile devices, including, but not limited to, smartphones, tablets, and watches. Successful exploitation of the most severe of these vulnerabilities could allow for privilege escalation in the context of the affected component. Depending on the privileges associated with the exploited component, an attacker could then install programs; view, change, or delete data; or create new accounts with full rights. 

There are indications that CVE-2024-53104 may be under limited, targeted exploitation 

Multiple vulnerabilities have been discovered in Google Android OS, the most severe of which could allow for privilege escalation in the context of the affected component. Details of the vulnerabilities are as follows: 

Tactic: Privilege Escalation (TA0004):

Technique: Exploitation for Privilege Escalation (T1068): 

• Multiple vulnerabilities in Framework that could allow for escalation of privilege(CVE-2024-49721, CVE-2024-49743, CVE-2024-49746, CVE-2025-0097, CVE-2025-0098, CVE-2025-0099).
• A vulnerability in Platform that could allow for escalation of privilege. (CVE-2025-0094)
•  Multiple vulnerabilities in System that could allow for escalation of privilege. (CVE-2025-0091, CVE-2025-0095, CVE-2025-0096)
• Multiple vulnerabilities in Kernel that could allow for escalation of privilege. (CVE-2024-53104, CVE-2025-0088)

Details of lower-severity vulnerabilities are as follows:

• Multiple vulnerabilities in Framework that could allow for information disclosure. (CVE-2023-40122, CVE-2023-40133, CVE-2023-40134, CVE-2023-40135, CVE-2023-40136, CVE-2023-40137, CVE-2023-40138, CVE-2023-40139, CVE-2024-0037, CVE-2025-0100)
• A vulnerability in Framework that could allow for denial of service. (CVE-2024-49741)
• Multiple vulnerabilities in System that could allow for information disclosure. (CVE-2024-49723, CVE-2024-49729)
• A vulnerability in Google Play system updates. (CVE-2024-49723)
• A vulnerability in Arm components. (CVE-2025-0015)
• Multiple vulnerabilities in Imagination Technologies. (CVE-2024-43705, CVE-2024-46973, CVE-2024-47892, CVE-2024-52935)
• Multiple vulnerabilities in MediaTek components. (CVE-2025-20634, CVE-2024-20141, CVE-2024-20142, CVE-2025-20635, CVE-2025-20636)
• A vulnerability in Unisoc components. (CVE-2024-39441)
• Multiple vulnerabilities in Qualcomm components. (CVE-2024-45569, CVE-2024-45571, CVE-2024-45582, CVE-2024-49832, CVE-2024-49833, CVE-2024-49834, CVE-2024-49839, CVE-2024-49843)
• Multiple vulnerabilities in Qualcomm closed-source components. (CVE-2024-38404, CVE-2024-38420) 

Successful exploitation of the most severe of these vulnerabilities could allow for privilege escalation in the context of the affected component. Depending on the privileges associated with the exploited component, an attacker could then install programs; view, change, or delete data; or create new accounts with full rights. 

We recommend the following actions be taken:

• Apply appropriate mitigations provided by Google to vulnerable systems immediately after appropriate testing. (M1051: Update Software)
• Safeguard 7.1: Establish and Maintain a Vulnerability Management Process: Establish and maintain a documented vulnerability management process for enterprise assets. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.
• Safeguard 7.4: Perform Automated Application Patch Management: Perform application updates on enterprise assets through automated patch management on a monthly, or more frequent, basis.
• Safeguard 7.5: Perform Automated Vulnerability Scans of Internal Enterprise Assets: Perform automated vulnerability scans of internal enterprise assets on a quarterly, or more frequent, basis. Conduct both authenticated and unauthenticated scans, using a SCAP-compliant vulnerability scanning tool.

• Use capabilities to detect and block conditions that may lead to or be indicative of a software exploit occurring. (M1050: Exploit Protection)
• Safeguard 10.5: Enable Anti-Exploitation Features: Enable anti-exploitation features on enterprise assets and software, where possible, such as Apple® System Integrity Protection (SIP) and Gatekeeper™.
• Safeguard 13.10 : Perform Application Layer Filtering: Perform application layer filtering. Example implementations include a filtering proxy, application layer firewall, or gateway.

• Restrict execution of code to a virtual environment on or in transit to an endpoint system. (M1048: Application Isolation and Sandboxing)
• Safeguard 16.8: Separate Production and Non-Production Systems: Maintain separate environments for production and non-production systems