Description
In arm_lpae_split_blk_unmap of io-pgtable-arm-common.c, 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.
Published: 2026-11-02
Score: n/a
EPSS: < 1% Very Low
KEV: No
Impact: Local Privilege Escalation
Action: Immediate Patch
AI Analysis

Impact

The vulnerability is a race condition in the arm_lpae_split_blk_unmap function of the Android kernel's io-pgtable-arm-common.c module. It can corrupt memory when concurrent threads unmap page table blocks. An attacker who can execute code locally on the device could exploit this to gain higher privileges, potentially allowing arbitrary modification of system services or access to protected data. The flaw does not require additional privileges or user interaction to trigger, meaning any local user can attempt the attack.

Affected Systems

The issue affects Android devices that run the kernel containing the io-pgtable-arm-common.c component with the vulnerable arm_lpae_split_blk_unmap implementation. Specifically, Google Android releases prior to the fix cited in the 2026-11-01 security bulletin. Devices using older kernel versions that have not applied the patch are at risk. No specific OS version was enumerated in the vendor notes, so any device running a legacy kernel is likely impacted until updated.

Risk and Exploitability

The CVSS score is not listed, but the EPSS is unavailable, and the vulnerability is not in the KEV catalog, indicating no known widespread exploitation yet. However, because the flaw requires only local access and no additional execution privileges, and it can be triggered by a race condition without user interaction, the risk of exploitation remains high for any device that is locally accessed by an attacker. The attack vector is inferred to be local, likely via a malicious app or privileged process that manipulates memory mapping calls. Regular patches and updates are needed to mitigate this risk.

Generated by OpenCVE AI on November 2, 2026 at 22:15 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest Android security update from Google that contains the kernel patch referenced in the 2026‑11‑01 bulletin
  • If the device cannot receive the update, restrict local administrative access, enable SELinux enforcing mode, and deny untrusted apps permission to perform memory mapping operations
  • Monitor device logs for abnormal pgtable activity and run integrity‑checking tools to detect memory corruption early

Generated by OpenCVE AI on November 2, 2026 at 22:15 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 02 Nov 2026 23:00:00 +0000

Type Values Removed Values Added
First Time appeared Google
Google android
Vendors & Products Google
Google android

Mon, 02 Nov 2026 22:45:00 +0000

Type Values Removed Values Added
Title memory corruption race condition in Android kernel leads to local privilege escalation
Weaknesses CWE-362

Mon, 02 Nov 2026 20:15:00 +0000

Type Values Removed Values Added
Description In arm_lpae_split_blk_unmap of io-pgtable-arm-common.c, 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.
References

cve-icon MITRE

Status: PUBLISHED

Assigner: google_android

Published:

Updated: 2026-11-03T15:24:30.548Z

Reserved: 2026-07-02T06:26:54.658Z

Link: CVE-2026-59043

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-11-02T20:17:57.593

Modified: 2026-11-03T14:52:42.467

Link: CVE-2026-59043

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-02T22:45:17Z

Weaknesses
  • CWE-362

    Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')