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

Out-of-bounds write in Android Kernel pKVM __pkvm_load_tracing

IdentifiersCVE-2025-48638CWE-787· Out-of-bounds Write

CVE-2025-48638 is a critical elevation-of-privilege vulnerability in the Android kernel’s protected KVM (pKVM) component. According to the provided description, the flaw exists in the __pkvm_load_tracing function in trace.c and is caused by improper input validation that can result in an out-of-bounds write. A successful exploit could corrupt memory in the pKVM context and enable local privilege escalation. The issue does not require user interaction, and the bulletin classifies it among the critical kernel issues addressed in the 2025-12-05 Android security patch level.

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.

Successful exploitation can lead to local escalation of privilege on affected Android devices. Because the flaw is in the pKVM subsystem, exploitation may undermine a security boundary intended to isolate sensitive code and data, potentially allowing an attacker to gain elevated execution context and compromise core device security guarantees.

Mitigation

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

Primary mitigation is prompt patching to Android security patch level 2025-12-05 or later. Where immediate patching is not possible, reduce exposure by limiting execution of untrusted local code and restricting installation of untrusted applications, since the issue is locally exploitable. Standard Android hardening measures such as Google Play Protect may reduce risk from malicious apps, but no complete mitigation short of applying the vendor/OEM patch is provided in the supplied content.

Remediation

Patch, then assume compromise.

Apply the Android December 2025 security updates, specifically the 2025-12-05 security patch level or later, which includes fixes for kernel and vendor issues such as CVE-2025-48638. OEMs and device administrators should ensure the relevant kernel update containing the fix for the pKVM __pkvm_load_tracing out-of-bounds write is integrated and deployed to supported devices.
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 activity5

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