Local crash loop via post-update memory check
Published Jan 24, 2023 · Updated Apr 3, 2025
Resource exhaustion in Google Cloud Android 10, 11, 12, 12L, and 13 allows local users to trigger a system crash loop via setting updates. SettingsState.java updates a setting before checking the memory-use limit, allowing oversized accumulated state to remain after the limit is exceeded. A malicious local app needs no additional execution privileges or user interaction; repeated updates exhaust memory and keep the device in an out-of-memory crash loop.
Summary
What happened
Resource exhaustion in Google Cloud Android 10, 11, 12, 12L, and 13 allows local users to trigger a system crash loop via setting updates. SettingsState.java updates a setting before checking the memory-use limit, allowing oversized accumulated state to remain after the limit is exceeded. A malicious local app needs no additional execution privileges or user interaction; repeated updates exhaust memory and keep the device in an out-of-memory crash loop.
The record
- CVE
- CVE-2023-20908
- Published
- Jan 24, 2023
- Updated
- Apr 3, 2025
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-400, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 24, 2023CVE publishedPublication date reported by the CVE source.
- Apr 3, 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-10 Android-11 Android-12 Android-12L Android-13
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.
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