Google Android kernel trace.c __pkvm_load_tracing out-of-bounds write
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $25k-$100k | 0.00 |
Summary
A vulnerability was found in Google Android kernel. It has been declared as critical. The impacted element is the function __pkvm_load_tracing of the file trace.c. Executing a manipulation can lead to out-of-bounds write.
This vulnerability appears as CVE-2025-48638. The attack requires local access. There is no available exploit.
Details
A vulnerability has been found in Google Android kernel and classified as critical. This vulnerability affects the function __pkvm_load_tracing of the file trace.c. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. The CWE definition for the vulnerability is CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
In __pkvm_load_tracing of trace.c, there is a possible out-of-bounds write due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
The advisory is available at android.googlesource.com. This vulnerability was named CVE-2025-48638 since 05/22/2025. The exploitation appears to be easy. Local access is required to approach this attack. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $25k-$100k at the moment (estimation calculated on 12/21/2025).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at EUVD (EUVD-2025-201735) and CERT Bund (WID-SEC-2025-2711). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Affected
- Lenovo BIOS
- Lenovo Computer
- 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.5VulDB Meta Temp Score: 6.5
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD 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: Out-of-bounds writeCWE: CWE-787 / CWE-119
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: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
05/22/2025 CVE reserved12/08/2025 Advisory disclosed
12/08/2025 VulDB entry created
12/21/2025 VulDB entry last update
Sources
Vendor: google.comAdvisory: android.googlesource.com
Status: Confirmed
CVE: CVE-2025-48638 (🔒)
GCVE (CVE): GCVE-0-2025-48638
GCVE (VulDB): GCVE-100-334858
EUVD: 🔒
CERT Bund: WID-SEC-2025-2711 - Android Patchday Dezember 2025: Mehrere Schwachstellen
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 12/08/2025 19:41Updated: 12/21/2025 17:42
Changes: 12/08/2025 19:41 (56), 12/08/2025 23:15 (11), 12/09/2025 01:21 (1), 12/21/2025 17:42 (7)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.