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
Unknown
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

AILast updated: 03/02/2026, 19:20:57 UTC

Technical Analysis

CVE-2025-48630 is a vulnerability identified in the drawLayersInternal function within SkiaRenderEngine.cpp, a core component of the Skia graphics library used by Google Android. The flaw involves a side channel information disclosure via the GPU cache, which can be accessed improperly due to insufficient isolation or leakage in the rendering engine. This side channel allows a local attacker to infer or extract sensitive data from the GPU cache, potentially leading to an escalation of privileges on the device. Notably, exploitation does not require additional execution privileges or user interaction, making it easier for malicious local applications or compromised processes to leverage this vulnerability. The affected Android versions include 14, 15, 16, and 16-qpr2, covering a broad range of currently supported and recent releases. While no public exploits have been reported, the vulnerability poses a significant risk due to the sensitive nature of GPU cache data and the potential for privilege escalation. The lack of a CVSS score indicates that the vulnerability is newly disclosed and pending further evaluation. The vulnerability highlights the risks inherent in GPU side channel attacks, which have become an increasing concern in modern graphics processing and mobile security.

Potential Impact

The primary impact of CVE-2025-48630 is the unauthorized disclosure of information through the GPU cache, compromising the confidentiality of data processed by the Android device's graphics subsystem. This can lead to local privilege escalation, allowing attackers to gain higher-level access without needing additional execution privileges or user interaction. Such escalation could enable attackers to bypass security controls, access sensitive user data, or prepare the device for further exploitation. The vulnerability affects a wide range of Android versions, potentially impacting millions of devices globally. Organizations relying on Android devices for sensitive operations, including enterprises and government agencies, face increased risk of data leakage and unauthorized access. The absence of known exploits in the wild currently limits immediate widespread impact, but the ease of exploitation and local nature of the attack vector mean that compromised or malicious local applications could leverage this vulnerability. This could also affect developers and users of applications that rely heavily on GPU rendering, as side channel leakage might expose proprietary or sensitive graphical data.

Mitigation Recommendations

To mitigate CVE-2025-48630, organizations and users should apply security patches from Google as soon as they become available for the affected Android versions (14 through 16-qpr2). Until patches are released, restricting local access to devices and limiting installation of untrusted or unnecessary applications can reduce the risk of exploitation. Employing application whitelisting and enhanced privilege management can help prevent malicious apps from gaining a foothold. Developers should review and harden GPU cache management and rendering engine code to minimize side channel leakage. Additionally, enabling device encryption and secure boot features can limit the impact of privilege escalation. Monitoring device behavior for unusual local activity or privilege escalations can provide early detection of exploitation attempts. Organizations should also maintain up-to-date inventories of Android devices and ensure timely updates to reduce exposure. Finally, educating users about the risks of installing unverified apps and the importance of device security hygiene is critical.

Need more detailed analysis?Upgrade to Pro Console

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/2/2026, 7:20:57 PM

Last updated: 3/3/2026, 5:53:05 AM

Views: 5

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 in Console -> Billing 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