Skip to main content
VulnerabilityPublished

CVE-2025-36917: Google Android · Denial of Service

Affects Google AndroidSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

To mitigate CVE-2025-36917, European organizations should prioritize the following actions: 1) Monitor vendor announcements and security advisories from Google and device manufacturers for patches or firmware updates addressing this vulnerability. 2) Deploy patches promptly once available to ensure the Android kernel is updated to a secure version. 3) Implement network-level protections such as firewalls and intrusion detection/prevention systems to detect and block suspicious traffic patterns that could exploit this vulnerability. 4) Restrict unnecessary network exposure of Android devices, especially those used in critical roles, to reduce the attack surface. 5) Employ device management solutions to maintain visibility and control over Android device configurations and update status. 6) Conduct regular security assessments and penetration tests focusing on mobile and embedded device security. 7) Educate IT and security teams about this vulnerability to ensure rapid response and incident handling. 8) Consider segmentation of critical Android-based systems to limit potential impact in case of exploitation. These measures go beyond generic advice by emphasizing proactive patch management, network defense, and operational controls tailored to the nature of this kernel-level DoS vulnerability.

Description

In SwDcpItg of up_L2commonPdcpSecurity.cpp, there is a possible denial of service due to an incorrect bounds check. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

References

Community reviews

Loading reviews…