CVE-2025-48611
In DeviceId of DeviceId.java, there is a possible desync in persistence due to a missing bounds check.
Published Mar 10, 2026 · updated Jun 17, 2026 · google android
In DeviceId of DeviceId.java, there is a possible desync in persistence due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Mar 10, 2026 · NIST NVD
Detected
In DeviceId of DeviceId.java, there is a possible desync in persistence due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Jun 17, 2026 · NIST NVD
Updated
In DeviceId of DeviceId.java, there is a possible desync in persistence due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Affected
- cpe google/androidversion unspecified
Sources
- CVE.orgVulnerability recordCVE-2025-48611
Official CVE identifier
cve.org - NIST NVDVulnerability recordCVE-2025-48611
In DeviceId of DeviceId.java, there is a possible desync in persistence due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
nvd.nist.gov