Local configuration disclosure via repeated pVM firmware copy
Published Dec 8, 2025 · Updated Dec 17, 2025
Information disclosure in the Android kernel allows local users to read protected-VM firmware configuration data through pKVM. __pkvm_guest_relinquish_to_host in mem_protect.c leaves the pVM firmware load address valid after a firmware page is returned, allowing a later donation to the same IPA range to re-fault and copy that page again. Exploitation requires low-privileged local access to an affected Android device with protected KVM and has no reported integrity or availability impact.
Summary
What happened
Information disclosure in the Android kernel allows local users to read protected-VM firmware configuration data through pKVM. __pkvm_guest_relinquish_to_host in mem_protect.c leaves the pVM firmware load address valid after a firmware page is returned, allowing a later donation to the same IPA range to re-fault and copy that page again. Exploitation requires low-privileged local access to an affected Android device with protected KVM and has no reported integrity or availability impact.
The record
- CVE
- CVE-2025-48610
- Published
- Dec 8, 2025
- Updated
- Dec 17, 2025
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 8, 2025CVE publishedPublication date reported by the CVE source.
- Dec 17, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Android kernel
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo