Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Android Kernel pKVM __pkvm_host_share_guest Integer Overflow OOB Write EoP

IdentifiersCVE-2026-0028CWE-190· Integer Overflow or Wraparound

CVE-2026-0028 is an Android kernel vulnerability in the pKVM memory protection code. In the function __pkvm_host_share_guest in mem_protect.c, an integer overflow can occur, resulting in a possible out-of-bounds write. The flaw is reachable locally and can be exploited without user interaction and without requiring additional execution privileges, leading to elevation of privilege on the device.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A successful exploit can trigger an out-of-bounds write in Android kernel pKVM host code, enabling local elevation of privilege. The associated CVSS v3.1 vector (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) indicates high impact to confidentiality, integrity, and availability.

Mitigation

If you can’t patch tonight, do this now.

No specific compensating controls are described in the provided content. As a practical mitigation, reduce exposure by ensuring devices are updated to the March 2026 security patch level (2026-03-05+) and limit local attack surface (e.g., restrict untrusted local code execution) until patches are deployed.

Remediation

Patch, then assume compromise.

Apply Android security updates that include the kernel/common fixes referenced for CVE-2026-0028 (Android Security Bulletin March 2026; patch level 2026-03-05 or later addresses all issues in the bulletin). Incorporate the upstream Android kernel common commits referenced in the CVE record (e.g., 986614312222d4b3bdcf16840cdb4abdaed8a42d, aff2255dbe38dc7c57bac8d3ba9feed989289b20, f3a4b4d4a1fe2aface7de74ac257b8705b6de472) into affected kernel branches.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleAndroidoperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity3

Community discussion across Reddit, Mastodon, and other social sources.