Persistent crash loop via oversized image decoding
Published Dec 8, 2025 · Updated Mar 6, 2026
Resource exhaustion in Android 14, 15, 16, and 16-qpr2 allows remote authenticated users to cause a persistent device crash loop. LocalImageResolver.onHeaderDecoded accepts oversized image dimensions without a hard decoding limit, allowing notification image decoding to consume device memory. No user interaction is required, but low-privileged access is reflected in the published CVSS assessments; the bounded impact is persistent service interruption through repeated crashes.
Summary
What happened
Resource exhaustion in Android 14, 15, 16, and 16-qpr2 allows remote authenticated users to cause a persistent device crash loop. LocalImageResolver.onHeaderDecoded accepts oversized image dimensions without a hard decoding limit, allowing notification image decoding to consume device memory. No user interaction is required, but low-privileged access is reflected in the published CVSS assessments; the bounded impact is persistent service interruption through repeated crashes.
The record
- CVE
- CVE-2025-48631
- Published
- Dec 8, 2025
- Updated
- Mar 6, 2026
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-400, T1499.003
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 8, 2025CVE publishedPublication date reported by the CVE source.
- Mar 6, 2026Record 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=14
- Affected versionversion=15
- Affected versionversion=16
- 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