CVE-2026-0031 is a vulnerability in the Android kernel affecting multiple functions in mem_protect.c. The flaw arises from an integer overflow that can result in an out-of-bounds write during memory protection handling. The issue is associated with kernel components, including the protected Kernel-based Virtual Machine (pKVM) context referenced in the March 2026 Android security updates. Successful exploitation can allow a local attacker to corrupt memory in kernel context and escalate privileges. The available information states that no user interaction is required and no additional execution privileges are needed to trigger the flaw.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical protected KVM (pKVM) elevation-of-privilege vulnerability that can enable privilege escalation across virtual machine boundaries.
Android Kernel component privilege escalation vulnerability.
Android Kernel component privilege escalation vulnerability.
Critical elevation-of-privilege vulnerability affecting the Android kernel pKVM subsystem.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.