Android Kernel mem_protect.c logic error leading to local EoP
CVE-2026-0038 is an Android kernel vulnerability in multiple functions in mem_protect.c. A logic error in the implementation can be exploited to achieve arbitrary code execution, resulting in local elevation of privilege. The published CVSS v3.1 vector is AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, indicating a local, low-complexity attack requiring no privileges and no user interaction, with high impact to confidentiality, integrity, and availability.
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.
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.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical hypervisor elevation-of-privilege vulnerability that may enable virtual machine escape and host control.
Android Kernel component privilege escalation vulnerability.
Android Kernel component privilege escalation vulnerability.
Vulnerability affecting the Android kernel hypervisor.
The version that knows your environment.
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.