CVE-2025-22404
8.4Google · Android
A use-after-free vulnerability in the Bluetooth stack of Android 15 allows for local privilege escalation via arbitrary code execution without user interaction.
Executive summary
A critical use-after-free vulnerability in the Android Bluetooth module allows an attacker to achieve local privilege escalation without requiring user interaction or elevated permissions.
Vulnerability
The vulnerability exists within the avct_lcb_msg_ind function of the Bluetooth stack, specifically in the avct_lcb_act.cc source file. It is a use-after-free flaw that allows for arbitrary code execution, requiring no special execution privileges or user interaction to trigger.
Business impact
The ability to achieve local privilege escalation represents a severe security risk, as it allows a malicious actor to bypass standard system protections to gain high-level control over the mobile device. Given the CVSS score of 8.4, this vulnerability is classified as High severity. Successful exploitation could lead to full device compromise, unauthorized access to sensitive user data, and the potential for persistent malware installation.
Remediation
Immediate Action: Update all Android 15 devices to the latest security patch level provided by the vendor, as specified in the March 2025 Android Security Bulletin.
Proactive Monitoring: Monitor device logs for unusual Bluetooth stack crashes or unexpected service restarts which may indicate attempts to trigger the use-after-free condition.
Compensating Controls: Ensure that Bluetooth is disabled on devices when not in active use to reduce the attack surface for proximity-based exploitation.
Exploitation status
Public Exploit Available: Unknown
Analyst recommendation
This vulnerability presents a significant risk to the integrity and confidentiality of Android devices. Security administrators must prioritize the deployment of the March 2025 security updates across all affected Android 15 units to mitigate the potential for local privilege escalation. Immediate patching is the only effective method to resolve this memory corruption issue.