CVE-2023-21216: Google Android · Elevation of privilege
Affects Google AndroidSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 4 Dec 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-25.
What to do
AI-suggested
To mitigate the risks posed by CVE-2023-21216, European organizations should implement a multi-layered approach: 1) Ensure all Android devices are updated promptly with security patches from device manufacturers or Google, as this vulnerability requires kernel-level fixes that can only be addressed through official updates. 2) Enforce strict mobile device management (MDM) policies that restrict installation of untrusted or third-party applications, reducing the risk of local exploitation. 3) Limit physical and local access to devices, especially in sensitive environments, to prevent attackers from gaining the local access needed to exploit this vulnerability. 4) Employ endpoint detection and response (EDR) solutions capable of monitoring for unusual kernel-level activities or privilege escalations on Android devices. 5) Educate users about the risks of installing apps from unknown sources and the importance of applying updates promptly. 6) For organizations deploying Android-based IoT or embedded systems, conduct thorough security assessments and consider network segmentation to isolate vulnerable devices. 7) Collaborate with vendors and monitor threat intelligence feeds for any emerging exploit code or attack campaigns targeting this vulnerability to respond swiftly. These targeted actions go beyond generic advice by focusing on controlling local access, enforcing update discipline, and monitoring kernel-level behaviors specific to this vulnerability.
Description
In PMRChangeSparseMemOSMem of physmem_osmem_linux.c, there is a possible arbitrary code execution due to a use after free. This could lead to local escalation of privilege in the kernel with no additional execution privileges needed. User interaction is not needed for exploitation.