Physical factory reset via missing DSU check
Published Dec 8, 2025 · Updated Dec 17, 2025
Denial of service in Android 13 through 16 allows physically proximate attackers to factory-reset a device while it is in DSU mode. RecoverySystem.rebootWipeUserData proceeds with the wipe without checking DynamicSystemManager.isInUse(), so DSU does not block the reset. Physical access is required, but no execution privileges or user interaction are needed; exploitation erases user data and interrupts device availability.
Summary
What happened
Denial of service in Android 13 through 16 allows physically proximate attackers to factory-reset a device while it is in DSU mode. RecoverySystem.rebootWipeUserData proceeds with the wipe without checking DynamicSystemManager.isInUse(), so DSU does not block the reset. Physical access is required, but no execution privileges or user interaction are needed; exploitation erases user data and interrupts device availability.
The record
- CVE
- CVE-2025-48614
- Published
- Dec 8, 2025
- Updated
- Dec 17, 2025
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-862, T1485
- Attack vector
- physical
- Privileges
- unauthenticated
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=13
- Affected versionversion=14
- Affected versionversion=15
- Affected versionversion=16
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