What is the CVSS score of CVE-2026-0152?

CVE-2026-0152 has a CVSS 3.1 base score of 7.8 (High). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.1%.

Which versions of Android Kernel are affected by CVE-2026-0152?

An unpatched local privilege escalation in the Android kernel (CVE-2026-0152, CVSS 7.8) affects Pixel and other Android devices, allowing a local attacker to gain root-equivalent privileges through…

How to fix or mitigate CVE-2026-0152?

Within 24 hours: Identify all Pixel and affected Android devices in your fleet and document current OS versions; restrict physical device access in high-risk environments. Within 7 days: Monitor Android Security & Privacy Year in Review and Google's security advisories for patch availability; test beta or stable builds in a controlled lab environment if patches are released. Within 30 days: Establish a patching schedule for affected devices and track vendor communications for backported fixes; prioritize patching in environments where device compromise would enable lateral network movement.

Android Kernel CVE-2026-0152

EUVD-2026-37186 HIGH

Buffer Overflow (CWE-119)

2026-06-16 Google_Devices

GHSA-8wwq-p6c4-57j3

Privilege Escalation Buffer Overflow Google

7.8

CVSS 3.1 · CISA-ADP

Severity by source

CISA-ADP PRIMARY

7.8 HIGH

AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

vuln.today AI

7.8 HIGH

Local attacker with low-privilege app access and no user interaction corrupts kernel memory for full privilege escalation, yielding total C/I/A impact.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from CISA-ADP.

CVSS VectorCISA-ADP

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 22, 2026 - 23:08 vuln.today

CVE Published

Jun 16, 2026 - 18:51 cve.org

UNKNOWN (no severity yet)

CVE Published

Jun 16, 2026 - 18:51 cve.org

HIGH 7.8

DescriptionCVE.org

In OSMMapPMRGeneric of pmr_os.c, there is a possible way to leverage a system call to system call to maliciously expand the VMA out of bounds 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.

AnalysisAI

Local privilege escalation in the Android kernel affects Pixel and other Android devices through a logic error in OSMMapPMRGeneric within pmr_os.c, the PowerVR/Imagination-style PMR (Physical Memory Resource) memory-management code. A local attacker chaining system calls can maliciously expand a Virtual Memory Area (VMA) out of bounds, corrupting kernel memory to gain root-equivalent privileges. Rated CVSS 7.8 with no public exploit identified at time of analysis; EPSS is 0.07% and CISA SSVC reports no observed exploitation, indicating this is a patched-early, not-yet-weaponized issue.

Technical ContextAI

The vulnerable routine OSMMapPMRGeneric in pmr_os.c handles mmap() of PMR (Physical Memory Resource) objects, a memory-management abstraction characteristic of the Imagination Technologies PowerVR GPU kernel driver commonly integrated into Android/Pixel kernels. A logic error in bounds handling lets a crafted sequence of system calls (mmap/related VMA operations) grow the mapped VMA beyond its intended size, mapping or exposing kernel-managed memory outside the allocation. This maps to CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer): the driver fails to enforce the boundary of the memory region during the mapping/expansion operation, enabling out-of-bounds access. Because the affected code is a device driver operating in kernel context, successful corruption directly undermines kernel-level memory isolation.

RemediationAI

Apply the Android security update that includes this fix: install the June 2026 (2026-06-01) security patch level or later as published in the Pixel Update Bulletin (https://source.android.com/docs/security/bulletin/pixel/2026/2026-06-01); Patch available per vendor advisory, though an exact numeric fix version is not enumerated in the provided data. Device owners should update to the latest OTA build for their model, and OEMs integrating the affected PowerVR/PMR driver should pull the corresponding upstream kernel fix. Where immediate patching is impossible, compensating controls are limited because the flaw is reachable by any locally running code: restrict installation to trusted applications and enforce app vetting/MDM allowlisting to reduce the chance of malicious local code, and where feasible on managed fleets restrict access to the GPU device nodes to trusted processes - noting this can break legitimate graphics/compute workloads and is not a substitute for the vendor patch.