dbcve.org
AndroidOperating system · Google

CVE-2025-48630

HIGH · 7.4 CVSS v3.1 Published 2026-03-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
79/100
Remediation priority · High
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a side-channel vulnerability in Skia's GPU rendering engine (SkiaRenderEngine.cpp) that allows unauthorized access to GPU cache memory. The flaw in the drawLayersInternal function leaks sensitive information through cache timing patterns, enabling a local attacker to escalate privileges without any additional execution privileges.

MitigationApply the vendor-released patch for Skia to address the side-channel vulnerability in the GPU cache access. As this is a local privilege escalation, minimize local attack surface and keep systems updated.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AndroidOperating system
Affected:= 14.0= 15.0= 16.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Android OS version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if The version listed is 14.0, 15.0, or 16.0 exactly (not a later patch version)
  2. Locate Skia library on the device
    Search for libskia.so in /system/lib64/ or /system/lib/ directories via ADB shell using 'find /system -name libskia.so 2>/dev/null'
    Affected if The library file exists, indicating Skia is present on the device
  3. Verify GPU rendering is in use
    Enable GPU rendering profiling in Developer Options (Profile GPU rendering > In apps) or check /sys/class/kgsl/kgsl-3d0/gpu_busy for GPU activity
    Affected if GPU rendering is enabled and actively used by applications on the device
  4. Identify processes using Skia GPU rendering
    Use 'ps -A | grep <app_name>' to list running processes, or check /proc/<pid>/maps for processes with libskia.so loaded
    Affected if Any user-facing application is running that relies on Skia for graphics rendering

A device is affected if it runs Android 14.0, 15.0, or 16.0 and has Skia's GPU rendering engine (libskia.so) in use, since the side-channel flaw in drawLayersInternal can leak GPU cache timing information to a local attacker.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-released patch for Skia to address the side-channel vulnerability in the GPU cache access. As this is a local privilege escalation, minimize local attack surface and keep systems updated.

Recommended fix Moderate confidence

Latest Android security update for your version (Android 14.x, 15.x, or 16.x) containing the SkiaRenderEngine.cpp timing attack fix

  1. 1. Navigate to Settings > Security & Privacy > Security Update on the Android device
  2. 2. Check for and install any available Android security updates
  3. 3. Ensure the device is running the latest available Android security patch level for your version (14.0, 15.0, or 16.0)
  4. 4. Verify the installed security patch level by checking Settings > About Phone > Android Security Patch Level
Caveat Security updates typically have minimal breaking changes; verify app compatibility after updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-48630 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-48630 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data