CVE-2026-0038: Google Android · Elevation of Privilege
Affects Google AndroidSource CVE Database V5
Not known to be exploited · CVSS 8.4 High.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 2 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GoogleAndroid | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2026-0038 effectively, organizations and users should: 1) Apply official security patches from Google or device manufacturers as soon as they become available, prioritizing kernel updates. 2) Restrict local access to devices by enforcing strong physical security controls and device management policies. 3) Limit installation of untrusted or third-party applications that could facilitate local exploitation. 4) Employ mobile device management (MDM) solutions to monitor device integrity and enforce security configurations. 5) Use runtime protection and behavior monitoring tools that can detect anomalous kernel-level activities. 6) Educate users about the risks of granting unnecessary permissions and the importance of installing updates promptly. 7) For organizations, segment networks to reduce the risk of compromised devices affecting critical infrastructure. 8) Monitor threat intelligence feeds for any emerging exploit code or attack campaigns targeting this vulnerability. 9) Consider deploying additional endpoint detection and response (EDR) solutions tailored for mobile environments to detect exploitation attempts. 10) Coordinate with vendors and security communities to stay informed about patch availability and best practices.
Description
In multiple functions of mem_protect.c, there is a possible way to execute arbitrary code due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
References
- android.googlesource.com/kernel/common/+/652b7b6bf9a62cc12c3a071bab4e92314f046739 (opens in a new tab)
- android.googlesource.com/kernel/common/+/f090d4b083a9ef4831f99e692c239542dd385cb4 (opens in a new tab)
- android.googlesource.com/kernel/common/+/7e1d15d29b7fe0f858926a8bcaf929b75db9e52a (opens in a new tab)
- android.googlesource.com/kernel/common/+/b23a5bfa1fb8f9525e21f095a87486a2bd856321 (opens in a new tab)
- android.googlesource.com/kernel/common/+/513ea99ae008b81dd266bf6e361627c058ddde41 (opens in a new tab)
- android.googlesource.com/kernel/common/+/1bf8033b56a45165602f8116e0a0d2e767f1e8ae (opens in a new tab)
- android.googlesource.com/kernel/common/+/d884f499434c224285c30d460681f1ce76a8cf1f (opens in a new tab)
- source.android.com/docs/security/bulletin/2026/2026-03-01 (opens in a new tab)