Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-48630: Information disclosure in Google Android

0
High
VulnerabilityCVE-2025-48630cvecve-2025-48630
Published: Mon Mar 02 2026 (03/02/2026, 18:42:17 UTC)
Source: CVE Database V5
Vendor/Project: Google
Product: Android

Description

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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/10/2026, 16:49:47 UTC

Technical Analysis

CVE-2025-48630 is a vulnerability in the SkiaRenderEngine component of Google Android, specifically within the drawLayersInternal function in SkiaRenderEngine.cpp. The flaw allows an attacker to exploit a side channel information disclosure in the GPU cache. This side channel leak can be leveraged by a local attacker to escalate privileges without requiring additional execution privileges or user interaction. The vulnerability affects multiple Android versions, including 14, 15, 16, and 16-qpr2, indicating a broad impact across recent Android releases. The underlying issue is classified as CWE-208, which involves exposure of sensitive information through side channels, potentially revealing GPU cache contents that could be used to infer or manipulate sensitive data. The CVSS v3.1 base score is 7.4, with vector AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, indicating that the attack requires local access with high attack complexity but no privileges or user interaction. The impact includes high confidentiality, integrity, and availability consequences, as the attacker can gain escalated privileges locally. No patches or exploits are currently publicly known, but the vulnerability's presence in core rendering engine components makes it a critical concern for Android device security. The vulnerability's exploitation could enable attackers to bypass security controls and access sensitive GPU cache data, potentially leading to further compromise of the device.

Potential Impact

The vulnerability poses a significant risk to Android devices worldwide, particularly those running affected versions 14 through 16-qpr2. By exploiting this side channel information disclosure, attackers with local access can escalate privileges, potentially gaining control over sensitive system components or user data. This can lead to unauthorized access to confidential information, manipulation of system integrity, and disruption of device availability. The absence of required user interaction increases the risk of stealthy exploitation, especially in scenarios where malicious apps or processes already have local access. Organizations relying on Android devices for sensitive communications, mobile workforce operations, or critical infrastructure management could face data breaches, operational disruptions, and erosion of trust. The broad version range affected means a large number of devices remain vulnerable until patches are applied. Although no known exploits are currently in the wild, the vulnerability's characteristics make it a prime target for attackers seeking local privilege escalation vectors.

Mitigation Recommendations

To mitigate CVE-2025-48630, organizations and users should: 1) Monitor for and apply official security patches from Google and device manufacturers as soon as they become available, as no patches are currently published. 2) Restrict installation of untrusted or unnecessary local applications to minimize the risk of local exploitation. 3) Employ mobile device management (MDM) solutions to enforce application whitelisting and limit local code execution capabilities. 4) Use Android security features such as SELinux enforcing mode and application sandboxing to contain potential exploits. 5) Regularly audit device logs and monitor for unusual local privilege escalation attempts or GPU cache access patterns. 6) Educate users on the risks of installing apps from unknown sources and encourage use of official app stores. 7) For high-security environments, consider additional endpoint detection and response (EDR) tools tailored for mobile platforms to detect anomalous behavior related to GPU cache or rendering engine exploitation. These steps go beyond generic advice by focusing on limiting local access vectors and preparing for patch deployment.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
google_android
Date Reserved
2025-05-22T18:12:31.616Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69a5db7cd1a09e29cb1cade0

Added to database: 3/2/2026, 6:48:28 PM

Last enriched: 3/10/2026, 4:49:47 PM

Last updated: 4/17/2026, 12:59:56 AM

Views: 87

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses