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-36912: Denial of service in Google Android

0
Medium
VulnerabilityCVE-2025-36912cvecve-2025-36912
Published: Thu Dec 11 2025 (12/11/2025, 19:35:31 UTC)
Source: CVE Database V5
Vendor/Project: Google
Product: Android

Description

In cellular modem, there is a possible denial of service due to a logic error in the code. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

AI-Powered Analysis

AILast updated: 12/11/2025, 20:16:01 UTC

Technical Analysis

CVE-2025-36912 is a vulnerability identified in the cellular modem component of the Android kernel. The flaw is due to a logic error in the modem's code, which can be triggered remotely to cause a denial of service (DoS) condition. This DoS can manifest as a device crash, reboot, or loss of cellular connectivity, effectively disrupting the affected device's availability. The vulnerability does not require any additional execution privileges, meaning an attacker does not need elevated rights on the device to exploit it. Furthermore, no user interaction is necessary, allowing exploitation without user awareness or consent. The affected product is the Android kernel, specifically the cellular modem subsystem, which is integral to mobile communication functions. Although no exploits have been reported in the wild, the vulnerability's characteristics make it a significant risk. The absence of a CVSS score means severity must be assessed based on impact and exploitability factors. The flaw's presence in the kernel level implies a broad impact surface across many Android devices, particularly those using cellular modems. The vulnerability was reserved in April 2025 and published in December 2025, indicating a recent discovery. No patches or mitigations have been linked yet, emphasizing the need for vigilance and rapid response once fixes become available.

Potential Impact

For European organizations, this vulnerability poses a risk of widespread disruption to mobile device availability and cellular communications. Organizations relying on Android devices for critical business functions, including field operations, communications, and mobile workforce management, could experience service interruptions. The denial of service could lead to loss of connectivity, impacting emergency services, logistics, and remote work capabilities. Additionally, sectors such as finance, healthcare, and government agencies that depend on secure and reliable mobile communications may face operational degradation. The lack of required user interaction or privileges means attackers could potentially target devices en masse, increasing the scale of impact. Disruptions could also affect IoT devices and embedded systems running Android kernels with cellular modems, expanding the threat beyond traditional smartphones. The potential for cascading effects on network infrastructure and service providers exists if large numbers of devices are affected simultaneously. Overall, the vulnerability threatens confidentiality indirectly by disrupting availability and potentially integrity if devices reboot unexpectedly during critical operations.

Mitigation Recommendations

European organizations should prioritize monitoring for updates from Google and Android device manufacturers to apply patches promptly once released. Until patches are available, network-level mitigations such as filtering or rate-limiting suspicious cellular traffic targeting modem components could reduce exposure. Deploying mobile device management (MDM) solutions to enforce security policies and monitor device health can help detect anomalies indicative of exploitation attempts. Organizations should conduct risk assessments to identify critical Android devices in their environment and consider temporary operational adjustments to reduce reliance on vulnerable devices. Collaboration with mobile network operators to share threat intelligence and coordinate defensive measures is advisable. Security teams should educate users about the risk, even though user interaction is not required, to maintain vigilance for unusual device behavior. Incident response plans should be updated to address potential mass device outages. Finally, organizations should evaluate alternative communication channels to maintain business continuity during potential disruptions.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Google_Devices
Date Reserved
2025-04-16T00:33:24.577Z
Cvss Version
null
State
PUBLISHED

Threat ID: 693b21637d4c6f31f7c35306

Added to database: 12/11/2025, 7:54:11 PM

Last enriched: 12/11/2025, 8:16:01 PM

Last updated: 12/12/2025, 3:07:32 AM

Views: 8

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