Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-22431: Denial of service in Google Android

0
Medium
VulnerabilityCVE-2025-22431cvecve-2025-22431
Published: Tue Sep 02 2025 (09/02/2025, 22:11:19 UTC)
Source: CVE Database V5
Vendor/Project: Google
Product: Android

Description

In multiple locations, there is a possible method for a malicious app to prevent dialing emergency services under limited circumstances due to a logic error in the code. This could lead to local denial of service until the phone reboots with no additional execution privileges needed. User interaction is not needed for exploitation.

AI-Powered Analysis

AILast updated: 09/10/2025, 04:50:30 UTC

Technical Analysis

CVE-2025-22431 is a medium-severity vulnerability affecting Google Android versions 13, 14, and 15. The vulnerability arises from a logic error in multiple locations within the Android codebase that handle emergency dialing functionality. Specifically, a malicious application, without requiring any user interaction or elevated privileges beyond limited app permissions, can exploit this flaw to prevent the device from dialing emergency services. This results in a local denial of service (DoS) condition that persists until the affected device is rebooted. The vulnerability does not compromise confidentiality or integrity but impacts availability by blocking critical emergency call functionality. The attack vector requires local access (AV:L) and low attack complexity (AC:L), with privileges required being low (PR:L), and no user interaction (UI:N) needed. The scope is unchanged (S:U), meaning the impact is confined to the vulnerable component without affecting other system components. The vulnerability is categorized under CWE-693, which relates to protection mechanism failures due to logic errors. No known exploits are currently reported in the wild, and no patches have been linked yet. This vulnerability is significant because it targets a fundamental safety feature of mobile devices, potentially endangering users who rely on emergency services access. The lack of required user interaction and low privilege level needed for exploitation increases the risk of widespread abuse, especially in environments where malicious apps can be installed or sideloaded.

Potential Impact

For European organizations, this vulnerability poses a notable risk primarily to employees and users who rely on Android devices for emergency communications. The inability to dial emergency services could have serious safety implications, especially for critical infrastructure personnel, healthcare workers, and field employees operating in hazardous environments. Organizations that provide mobile devices to their workforce may face liability and reputational damage if employees are unable to access emergency services during incidents. Furthermore, sectors such as public safety, transportation, and utilities that depend on reliable mobile communication could experience operational disruptions. Although the vulnerability does not allow data theft or system takeover, the denial of emergency calls could indirectly affect organizational resilience and employee safety. Given the medium CVSS score of 5.5 and the ease of exploitation without user interaction, attackers could deploy malicious apps via social engineering or compromised app stores to target specific organizations or regions. The impact is compounded in scenarios where device rebooting is delayed or impractical, prolonging the denial of service condition.

Mitigation Recommendations

To mitigate this vulnerability, European organizations should implement a multi-layered approach: 1) Enforce strict application vetting policies by restricting app installations to trusted sources such as the official Google Play Store and employing Mobile Device Management (MDM) solutions to control app permissions and installations. 2) Monitor device behavior for anomalies related to emergency call functionality and implement alerts for failed emergency call attempts. 3) Educate users about the risks of installing untrusted applications and the importance of promptly rebooting devices if emergency call issues are suspected. 4) Coordinate with device vendors and Google to prioritize patch deployment once available, and ensure timely updates of Android devices across the organization. 5) For critical roles, consider deploying secondary communication devices or alternative emergency communication methods as a contingency. 6) Conduct regular security audits and penetration testing focused on mobile device security to detect potential exploitation attempts. These measures go beyond generic advice by focusing on operational controls, user awareness, and proactive monitoring tailored to the specific nature of this vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
google_android
Date Reserved
2025-01-06T17:45:03.362Z
Cvss Version
null
State
PUBLISHED

Threat ID: 68b77091ad5a09ad00e938c5

Added to database: 9/2/2025, 10:32:49 PM

Last enriched: 9/10/2025, 4:50:30 AM

Last updated: 10/17/2025, 4:58:48 AM

Views: 16

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats