CVE-2025-48568
Race Condition Lockscreen Bypass in Android Enables Privilege Escalation
Publication date: 2026-03-02
Last updated on: 2026-03-06
Assigner: Android (associated with Google Inc. or Open Handset Alliance)
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| android | 14.0 | |
| android | 15.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-362 | The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a possible lockscreen bypass caused by a race condition occurring in multiple locations within the system.
It allows an attacker to escalate privileges locally without needing any additional execution privileges or user interaction.
How can this vulnerability impact me? :
The vulnerability can lead to local escalation of privilege, meaning an attacker could gain higher access rights on the device without needing to execute additional code or require user interaction.
This could allow unauthorized access to sensitive information or system functions that are normally protected by the lockscreen.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know