EUVD-2026-115583
GHSA-c3xm-9g6q-v3qm
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRun unprivileged code on device
-
ExploitTrigger logic error in fork.c
-
ExecutionExploit kernel use-after-free
-
ImpactEscalate to kernel privileges
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires the ability to execute local unprivileged code on an affected Android device (AV:L); per the CVSS vector and the description's 'no additional execution privileges needed,' no prior privileges (PR:N) and no user interaction (UI:N) are required. The flaw lies in a logic error across multiple functions of fork.c that produces a use-after-free in the kernel process-creation path; the exact trigger sequence is not described in the available sources. Exploitation is limited to attackers who already have local access/code execution on the device and only against devices running an unpatched/vulnerable kernel (fixed by the referenced android.googlesource commits and the November 2026 Android Security Bulletin); it is not remotely reachable. |
| Impact | This is a genuine high-severity local privilege escalation in the Android/Linux fork.c process-creation code (CWE-416 use-after-free), but the real-world urgency signals are more measured than the 8.4 base score alone suggests. The CVSS vector (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) indicates a local, low-complexity attack needing no privileges or user interaction, with total confidentiality, integrity and availability impact - consistent with SSVC 'Technical Impact: total'. However, SSVC reports 'Exploitation: none' and 'Automatable: no', the vuln.today priority is 'this_week' (not act_now/emergency), it is NOT in CISA KEV, and no EPSS score is provided. There is no public exploit code and no PoC reference among the inputs. In short: a serious, fixable kernel bug worth prompt patching on the normal Android bulletin cadence, not an emergency. Note an apparent tension worth flagging: the vector sets PR:N while the flaw is a local kernel UAF; this aligns with the description's 'no additional execution privileges needed,' meaning any local context (e.g., an unprivileged app) can reach the path - verify against the vendor's own exploitability guidance. |
| Exploit ScenarioDerived | A malicious or compromised unprivileged app running locally on an affected Android device triggers the logic error in fork.c's process-creation path, causing a use-after-free in the kernel. By controlling the freed object's reuse, the attacker corrupts kernel memory to gain kernel-level privileges. No user interaction is required, but local code execution on the device is a prerequisite; no public exploit code is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 02, 2026
A local privilege escalation exists in the Android kernel's process-creation code (fork.c), where a logic error across multiple functions leaves a freed object reachable and produces a use-after-free (CWE-416). Per the CVSS vector (AV:L/PR:N/UI:N), any party able to run unprivileged code on an affected device can trigger it without additional execution privileges or user interaction, and successful exploitation yields high confidentiality, integrity and availability impact at kernel level. Exploitation requires local code execution on the device and is not remotely reachable; SSVC records exploitation as none and no public exploit has been identified at time of analysis, so despite the 8.4 base score the practical urgency is measured rather than emergency-grade, with fixes delivered through the November 2026 Android Security Bulletin.
RemediationAI
Apply the kernel fixes published in the November 2026 Android Security Bulletin (https://source.android.com/docs/security/bulletin/2026/2026-11-01), which is the vendor-released remediation path for this issue; the corresponding upstream changes are the Android common kernel commits efe16a3021b9f95eb1cb83e98d0d1db9bff94ce4 and 009c5006c969826d37a2c5fc2721a7bb20d72555. Device owners should install the monthly Android security update at the November 2026 patch level or later as soon as their OEM/carrier makes it available, since kernel fixes only reach handsets through that channel; kernel and platform maintainers building their own images should cherry-pick both commits. Until the update is deployed, the exposure is limited to attackers who already hold local code execution on the device, so reducing the ability to run untrusted local code - restricting sideloaded or untrusted applications and developer/adb access on high-value devices - lowers practical risk, but these are partial measures only and updating the kernel remains the complete fix.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is a use-after-free (CWE-416) rooted in a logic error within fork.c, the kernel source file that implements process and thread creation. The CPE entry cpe:2.3:a:google:android:*:*:*:*:*:*:*:* and the EUVD affected-version data ('Android Android kernel') indicate the vulnerable component is the Android common kernel shipped with Android devices rather than an application-layer package. Because the defect sits in the process-creation path, it is reachable from ordinary unprivileged user-space code: an attacker who already has local code execution can drive the faulty logic and operate on a kernel object after it has been freed, which in kernel context typically permits memory corruption leading to escalation to kernel (root) privileges. The CVSS vector rates attack complexity as low (AC:L) and scope as unchanged (S:U), with high impact on confidentiality, integrity and availability. The exact trigger sequence and the specific fork.c functions involved are not described in the available sources; the upstream corrections are visible as two Android common kernel commits (efe16a3021b9f95eb1cb83e98d0d1db9bff94ce4 and 009c5006c969826d37a2c5fc2721a7bb20d72555) referenced alongside the November 2026 Android Security Bulletin.
Know when Android gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Local kernel UAF reachable from unprivileged local code with no interaction, so AV:L/AC:L/PR:N/UI:N; kernel-privilege compromise yields full C:H/I:H/A:H within the OS (S:U).
Primary rating from Vendor (google_android).
CVSS VectorVendor: google_android
Lifecycle Timeline
3DescriptionCVE.org
In multiple functions of fork.c, there is a possible use after free 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.
Articles & Coverage 2
Executive ViewAI
CVE-2026-58825 is a high-severity local privilege escalation vulnerability in the Android kernel, affecting devices running unpatched Android versions. Any unprivileged app or user on the device can exploit it to gain kernel-level control, compromising data confidentiality, integrity, and availability without user interaction. Although no public exploit exists yet, the broad attack surface across managed mobile fleets warrants proactive management.
No vendor-released patch identified at time of analysis. Interim mitigations include enforcing mobile device management policies to prevent sideloading of untrusted applications, minimizing the number of unprivileged apps on sensitive devices, and applying the November 2026 Android Security Bulletin update as soon as it is available from device manufacturers.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows and OS X and before 11.2.202.466
Integer underflow in the MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in mediaserver in A
Android 3.0 through 4.1.x on Disney Mobile, eAccess, KDDI, NTT DOCOMO, SoftBank, and other devices does not properly imp
Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android bef
Apktool versions 2.9.1 and prior contain a path traversal vulnerability when processing Android APK files. Malicious APK
An elevation of privilege vulnerability in the Android system (art). Rated high severity (CVSS 7.8), this vulnerability
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows
Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows
Android 1.6 Donut through 4.2 Jelly Bean does not properly check cryptographic signatures for applications, which allows
luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.
The Broadcom Wi-Fi driver in the kernel in Android 4.x before 4.4.4, 5.x before 5.1.1 LMY49G, and 6.x before 2016-02-01
Exploit-DB