CVE-2025-48615
Modified Modified - Updated After Analysis
BaseFortify

Publication date: 2025-12-08

Last updated on: 2026-06-01

Assigner: Android (associated with Google Inc. or Open Handset Alliance)

Description
In getComponentName of MediaButtonReceiverHolder.java, there is a possible desync in persistence due to resource exhaustion. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-08
Last Modified
2026-06-01
Generated
2026-06-16
AI Q&A
2025-12-08
EPSS Evaluated
2026-06-15
NVD
Affected Vendors & Products
Showing 4 associated CPEs
Vendor Product Version / Range
google android 13.0
google android 14.0
google android 15.0
google android 16.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-770 The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
CWE-400 The product does not properly control the allocation and maintenance of a limited resource.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability occurs in the getComponentName function of MediaButtonReceiverHolder.java, where a possible desynchronization in persistence happens due to resource exhaustion. This flaw can be exploited locally to escalate privileges without needing any additional execution privileges or user interaction.

Impact Analysis

The vulnerability can allow an attacker with local access to escalate their privileges on the affected system without requiring user interaction or additional execution privileges, potentially leading to unauthorized actions or access.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-48615. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart