Google Android 14/15/16/16-qpr2 SkiaRenderEngine.cpp drawLayersInternal information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google Android 14/15/16/16-qpr2. It has been classified as problematic. Affected by this issue is the function drawLayersInternal of the file SkiaRenderEngine.cpp. The manipulation leads to information disclosure.
This vulnerability is uniquely identified as CVE-2025-48630. Local access is required to approach this attack. No exploit exists.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability, which was classified as problematic, has been found in Google Android 14/15/16/16-qpr2. This issue affects the function drawLayersInternal of the file SkiaRenderEngine.cpp. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:
In drawLayersInternal of SkiaRenderEngine.cpp, there is a possible way to access the GPU cache due to side channel information disclosure. 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 at source.android.com. The identification of this vulnerability is CVE-2025-48630 since 05/22/2025. The exploitation is known to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 03/09/2026). MITRE ATT&CK project uses the attack technique T1592 for this issue.
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-0569). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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.0VulDB Meta Temp Score: 6.0
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.4
NVD Vector: 🔒
ADP CISA Base Score: 7.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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
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 reserved03/02/2026 Advisory disclosed
03/02/2026 VulDB entry created
03/09/2026 VulDB entry last update
Sources
Vendor: google.comAdvisory: source.android.com
Status: Confirmed
CVE: CVE-2025-48630 (🔒)
GCVE (CVE): GCVE-0-2025-48630
GCVE (VulDB): GCVE-100-348437
CERT Bund: WID-SEC-2026-0569 - Google Android: Mehrere Schwachstellen
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 03/02/2026 20:23Updated: 03/09/2026 21:14
Changes: 03/02/2026 20:23 (57), 03/04/2026 11:48 (20), 03/09/2026 21:14 (6)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.