CVE-2025-48611: Critical severity Google Android vulnerability

Published Mar 10, 2026
·
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 Software

1 affected component
Google Android

Event History

Mar 10, 2026
CVE Published
via MITRE·07:33 PM
Data Sourced
via MITRE·07:33 PM
DescriptionSeverity
Data Sourced
via NVD·08:16 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-48611?

CVE-2025-48611 is classified as a moderate severity vulnerability due to potential local escalation of privilege.

2

How do I fix CVE-2025-48611?

To mitigate CVE-2025-48611, ensure that you are running the latest version of the affected Google Android software that includes the security patch.

3

What is the exploitation impact of CVE-2025-48611?

CVE-2025-48611 could lead to local escalation of privilege, allowing an attacker to gain higher access to system resources.

4

Is user interaction required to exploit CVE-2025-48611?

No, user interaction is not needed for the exploitation of CVE-2025-48611.

5

Which software is affected by CVE-2025-48611?

CVE-2025-48611 affects Google Android across various versions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203