In multiple locations, there is a possible way to modify coprocessor instruction and data memory from non-secure software due to an insecure default value. This could lead to local escalation of privilege with System execution privileges needed. User interact…
CVE-2025-48633Android Framework Information Disclosure Vulnerability
Known exploited — Android Framework Information Disclosure Vulnerability
CISA confirmed this vulnerability is used in real attacks on 02.12.2025. Remediation deadline for US federal agencies: 23.12.2025.
Required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. https://source.android.com/docs/security/bulletin/2025-12-01 ; https://nvd.nist.gov/vuln/detail/CVE-2025-48633
Description
In hasAccountsOnAnyUser of DevicePolicyManagerService.java, there is a possible way to add a Device Owner after provisioning due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Data: CVE.org, NVD, CISA KEV, FIRST EPSS, Ubuntu. Published as the sources state it, in English.
Affected products and versions
References and patches
CPE matches (NVD) (4)
cpe:2.3:o:google:android:13.0:*:*:*:*:*:*:*cpe:2.3:o:google:android:14.0:*:*:*:*:*:*:*cpe:2.3:o:google:android:15.0:*:*:*:*:*:*:*cpe:2.3:o:google:android:16.0:*:*:*:*:*:*:*