CVE-2025-48638 is a critical elevation-of-privilege vulnerability in the Android kernel affecting the protected KVM (pKVM) subsystem. The flaw is located 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. By supplying crafted input that reaches this code path, a local attacker can corrupt memory in kernel context. Because the issue resides in pKVM, exploitation may undermine a security boundary intended to isolate sensitive code and data on Android devices.
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.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical elevation-of-privilege vulnerability in the Android Kernel's Protected KVM (PKVM) subsystem.
Critical kernel-level elevation-of-privilege vulnerability in Android affecting IOMMU, potentially undermining device/memory isolation.
Critical local elevation-of-privilege vulnerability in the kernel pKVM subcomponent (as described), addressed in the 2025-12-05 patch level via upstream kernel patches.
A critical local escalation of privilege vulnerability in the pKVM subcomponent of the Android kernel.
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.