CVE-2025-48577
Race Condition in KeyguardViewMediator Causes Lockscreen Bypass
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 | |
| android | 16.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 exists in multiple functions of the KeyguardViewMediator.java component, where a race condition can occur. This race condition may allow an attacker to bypass the lockscreen.
Exploitation does not require any user interaction or additional execution privileges.
How can this vulnerability impact me? :
The vulnerability could lead to a local escalation of privilege, meaning an attacker with local access could gain higher privileges on the device without needing extra permissions.
Because it allows bypassing the lockscreen, sensitive information or device functionality could be accessed without proper authorization.
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