CVE-2026-58825
Received Received - Intake

Use After Free in Android Kernel

Publication date: 2026-11-02

Last updated on: 2026-11-02

Assigner: Android (associated with Google Inc. or Open Handset Alliance)

Description
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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-02
Last Modified
2026-11-02
Generated
2026-11-02
AI Q&A
2026-11-02
EPSS Evaluated
N/A
NVD
CVE-2026-58825

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
Google Android Android kernel

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-416 The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a use-after-free issue in the Linux kernel's fork.c file. It occurs due to a logic error that allows a process to free memory while still retaining a reference to it. This can lead to local privilege escalation without needing additional execution privileges or user interaction.

Detection Guidance

This vulnerability involves a use-after-free in fork.c, which may not have direct detection commands. Monitor kernel logs for crashes or unusual behavior in process management. Check for abnormal /proc/<pid>/dmabuf_rss values or related dmabuf accounting issues. Review system logs for unshare-related errors or privilege escalation attempts.

Impact Analysis

An attacker could exploit this to gain elevated privileges on your system, potentially allowing them to take control of your device or access sensitive data. Since no user interaction is required, the risk is higher as attacks can happen silently in the background.

Mitigation Strategies

Apply the latest kernel patches from your vendor. Restrict unshare system calls via seccomp or AppArmor policies. Monitor for suspicious process behavior. Update Android devices to the latest security patch level if affected.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-58825. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...