CVE-2025-48617: High severity Google Android vulnerability
In overrideConfig of CarrierConfigLoader.java, there is a possible way to bypass UID check due to a permissions bypass. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Compensating control
Restrict local and physical access to affected devices and accounts to trusted personnel only. Use host-based controls (application whitelisting, local firewall rules, endpoint protection) to reduce the ability of untrusted local code to execute.
- Compensating control
Prevent installation or execution of untrusted applications by enforcing centralized app-installation policies (for example via MDM) and by removing or disabling unnecessary local services that increase the attack surface.
- Operational
Monitor and audit system and security logs for signs of UID or permission bypass and any unexpected privilege escalations. Investigate and remediate any suspicious activity promptly.
- Operational
Apply vendor-supplied patches or updates that address this issue as soon as they become available.
Event History
Frequently Asked Questions
What is the severity of CVE-2025-48617?
CVE-2025-48617 has a risk score of 65, indicating a medium level of severity.
How does CVE-2025-48617 affect Google Android?
CVE-2025-48617 allows a local escalation of privilege due to a permissions bypass in the CarrierConfigLoader.java.
Who is affected by CVE-2025-48617?
Any user running a vulnerable version of Google Android could potentially be affected by CVE-2025-48617.
What is required to exploit CVE-2025-48617?
Exploitation of CVE-2025-48617 does not require any user interaction and does not need additional execution privileges.
How can I mitigate the risk of CVE-2025-48617?
To mitigate the risk of CVE-2025-48617, ensure your Google Android device is updated to the latest security patches.