CVE-2026-0152: In OSMMapPMRGeneric of pmr_os
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.
Metrics
- CVSS v3.1
- 7.8
- Severity
- HIGH
- Fixed in
- —
- Affected Products
- 1
HarborGuard Analysis
Synopsis
This is a local privilege escalation vulnerability in the Android kernel, specifically in the OSMMapPMRGeneric function of pmr_os.c. A logic error allows an attacker with a low-privilege shell on the device to issue a crafted system call that expands a Virtual Memory Area (VMA) out of its intended bounds, violating kernel memory isolation. Successful exploitation gives the attacker full read, write, and execution control at the kernel level, effectively rooting the device. No fix version has been published yet; HarborGuard is tracking the upstream advisory for patch availability.
HarborGuard Coverage
Detection is available across every HarborGuard environment: the CVE is ingested from upstream feeds within minutes of publication and matched against customer images, including custom-built Android kernel images, as soon as they appear in connected registries or CI pipelines. Any image carrying an affected Android kernel version is flagged automatically without manual intervention.
AvailableHarborGuard is capable of scoring this finding at CVSS 7.8 HIGH and weighting it further against each environment's compliance policy, for example stricter thresholds for production or regulated workloads. Findings are routed to the inbox or ticketing integration configured for the affected workload's owner within each customer organization.
AvailableBecause no upstream fix version has been published for CVE-2026-0152, HarborGuard re-checks the advisory on every ingest cycle and will make a patched-image rebuild available as soon as the Android kernel maintainers ship a corrected release. For customers with auto-remediation enabled, the rebuild, regression run, and PR against affected workloads will be triggered automatically at that point without requiring manual follow-up.
Pending upstreamExploit Conditions
- Network reachabilityNot required
The attacker needs an existing shell or process on the host; no network access to the device is required to trigger the vulnerable code path.
- AuthenticationRequired
Any low-privilege local account is sufficient; no administrative or elevated credentials are needed before exploitation.
- Victim interactionNot required
No user interaction is required; the attacker can execute the exploit entirely on their own without social engineering or user assistance.
- Attack complexityDetail
Attack complexity is low, meaning the exploit is reliable and condition-free with no race conditions or special memory layout requirements.
Blast Radius
- Reads arbitrary kernel memory, including credentials, cryptographic keys, and session tokens stored by other processes.
- Writes to kernel data structures, allowing modification of security policies, file system permissions, or process privilege levels.
- Achieves full kernel-level code execution, effectively rooting the device and bypassing all OS-enforced access controls.
- Crashes or destabilizes the kernel at will, causing device outages or denial of service for all co-resident processes.
How HarborGuard Handles This
Available on HarborGuard: detection for CVE-2026-0152 is active across all connected environments, flagging any container image built on or shipping an affected Android kernel version. Because no upstream patch exists as of the CVE publication date, HarborGuard monitors the advisory on every ingest cycle. In the interim, customers can apply compensating controls surfaced through HarborGuard's policy engine, including network-policy isolation to limit lateral movement from a compromised container, egress filtering to reduce post-exploitation reach, and workload admission rules that restrict which images are permitted to run in sensitive namespaces. For customers with auto-remediation enabled, a patched-image rebuild, regression test run, and PR against affected workloads will be triggered automatically the moment the Android kernel maintainers publish a fix, with no manual follow-up required.
- Google / AndroidAndroid kernel
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H