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

Android Kernel pKVM out-of-bounds write in __host_check_page_state_range (mem_protect.c)

IdentifiersCVE-2026-0030CWE-787· Out-of-bounds Write

CVE-2026-0030 is an Android kernel vulnerability in the function __host_check_page_state_range within mem_protect.c. The issue is a possible out-of-bounds write caused by an incorrect bounds check. Successful exploitation can result in a local elevation of privilege. The provided description indicates no user interaction is required and no additional execution privileges are needed to exploit the flaw.

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.

Local elevation of privilege in the Android kernel/pKVM context due to an out-of-bounds write, with high potential impact to confidentiality, integrity, and availability (CVSS v3.1 vector AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Mitigation

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

No specific mitigations are provided in the supplied content beyond patching. As a risk-reduction measure, limit local attack surface where feasible (e.g., restrict untrusted local code execution paths), but the authoritative mitigation per the content is to deploy the kernel updates from the Android security bulletin/associated kernel commits.

Remediation

Patch, then assume compromise.

Apply the Android security updates that include the upstream fixes for CVE-2026-0030 (Android Security Bulletin March 2026; kernel/common patches referenced by commits 986614312222d4b3bdcf16840cdb4abdaed8a42d, aff2255dbe38dc7c57bac8d3ba9feed989289b20, and f3a4b4d4a1fe2aface7de74ac257b8705b6de472). Ensure devices are updated to a security patch level that includes the 2026-03-05 kernel fixes as applicable.
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 activity4

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