Permanent denial of service via resource exhaustion
Published Dec 8, 2025 · Updated Dec 8, 2025
Uncontrolled resource consumption in Google Android 16 QPR2 allows local users to cause a permanent denial of service without interaction. Google identifies the Framework component and multiple affected locations but has not disclosed which operations exhaust resources or what inputs reach them. A low-privileged local user can trigger the availability-only failure without user interaction, and Google describes the resulting denial of service as permanent.
Summary
What happened
Uncontrolled resource consumption in Google Android 16 QPR2 allows local users to cause a permanent denial of service without interaction. Google identifies the Framework component and multiple affected locations but has not disclosed which operations exhaust resources or what inputs reach them. A low-privileged local user can trigger the availability-only failure without user interaction, and Google describes the resulting denial of service as permanent.
The record
- CVE
- CVE-2025-48569
- Published
- Dec 8, 2025
- Updated
- Dec 8, 2025
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-770, CWE-400, T1642
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 8, 2025CVE publishedPublication date reported by the CVE source.
- Dec 8, 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=16-qpr2
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