CVE-2026-58728

Received Received - Intake

Memory Corruption in ARM64_TLBI Due to Race Condition

Publication date: 2026-09-15

Last updated on: 2026-09-18

Assigner: Google Devices

Description

In ARM64_TLBI of mmu.h, there is a possible memory corruption due to a race condition. 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-09-15

Last Modified

2026-09-18

Generated

2026-10-06

AI Q&A

2026-09-16

EPSS Evaluated

2026-10-04

NVD

CVE-2026-58728

EUVD

EUVD-2026-79011

Affected Vendors & Products

Vendor	Product	Version / Range
google	android	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-362	The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Attack-Flow Graph

Executive Summary

This is a race condition vulnerability in ARM64_TLBI of mmu.h that could lead to memory corruption. It allows local privilege escalation without needing extra execution privileges or user interaction.

Impact Analysis

An attacker could exploit this to gain higher privileges on your system, potentially allowing them to take control of your device or access sensitive data.

Compliance Impact

This vulnerability could lead to local privilege escalation, potentially allowing unauthorized access to sensitive data. This may impact compliance with GDPR (data protection) and HIPAA (healthcare data privacy) by increasing the risk of data breaches or unauthorized access to personal or health information.

Mitigation Strategies

Apply the latest security patches or updates from ARM or your device manufacturer to address the race condition in ARM64_TLBI of mmu.h. Monitor vendor advisories for specific fixes.

Hi! I’m here to help you understand CVE-2026-58728. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70