Google Android 16 apexd.cpp VerifyNoOverlapInSessions unusual condition
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $5k-$25k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in Google Android 16. Affected by this vulnerability is the function VerifyNoOverlapInSessions of the file apexd.cpp. Executing a manipulation can lead to Local Privilege Escalation.
This vulnerability is handled as CVE-2025-48581. It is possible to launch the attack on the local host. There is not any exploit available.
Applying a patch is advised to resolve this issue.
Details
A vulnerability classified as problematic was found in Google Android 16. This vulnerability affects the function VerifyNoOverlapInSessions of the file apexd.cpp. The manipulation with an unknown input leads to a local privilege escalation vulnerability. The CWE definition for the vulnerability is CWE-754. The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
In VerifyNoOverlapInSessions of apexd.cpp, there is a possible way to block security updates 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.
The advisory is shared for download at source.android.com. This vulnerability was named CVE-2025-48581 since 05/22/2025. The exploitation appears to be easy. The attack needs to be approached locally. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 06/02/2026).
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2025-1944). VulDB is the best source for vulnerability data and more expert information about this specific topic.
Affected
- Google Android
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.7
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
ADP CISA Base Score: 8.4
ADP CISA Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Unusual conditionCWE: CWE-754
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔒
Timeline
05/22/2025 CVE reserved09/04/2025 Advisory disclosed
09/04/2025 VulDB entry created
06/02/2026 VulDB entry last update
Sources
Vendor: google.comAdvisory: source.android.com
Status: Confirmed
CVE: CVE-2025-48581 (🔒)
GCVE (CVE): GCVE-0-2025-48581
GCVE (VulDB): GCVE-100-322696
CERT Bund: WID-SEC-2025-1944 - Android Patchday September 2025: Multiple Vulnerabilities
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 09/04/2025 22:06Updated: 06/02/2026 07:00
Changes: 09/04/2025 22:06 (55), 09/06/2025 04:52 (2), 09/07/2025 18:09 (7), 11/18/2025 06:27 (1), 06/02/2026 07:00 (11)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.