Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Medium

Android Framework emergency dialing denial of service in AppOpsService.verifyAndGetBypass

IdentifiersCVE-2025-48590CWE-400· Uncontrolled Resource Consumption

CVE-2025-48590 is an Android Framework denial-of-service vulnerability in AppOpsService.java, specifically in the verifyAndGetBypass method. According to the provided description, a malicious application can exploit resource exhaustion under limited circumstances to prevent dialing emergency services. The issue does not require additional execution privileges and does not require user interaction, indicating that a locally installed app can trigger the condition directly from its existing app context.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can cause a local denial of service affecting emergency call functionality, specifically preventing the device from dialing emergency services under limited circumstances. The security impact is significant because it interferes with a safety-critical device capability, even though the bug does not provide code execution or privilege escalation.

Mitigation

If you can’t patch tonight, do this now.

Until patches are deployed, mitigation options are limited because exploitation requires no user interaction and no additional privileges beyond a malicious local app. Practical risk reduction measures include restricting installation of untrusted applications, enforcing application allow-listing in managed environments, using only trusted app distribution channels, and rapidly deploying the December 2025 Android security update or vendor-equivalent firmware.

Remediation

Patch, then assume compromise.

Apply the Android security updates that include the fix for CVE-2025-48590. The provided content indicates this issue is addressed in Google’s December 2025 Android Security Bulletin, and devices updated to the 2025-12-05 patch level are described as fully remediated for disclosed issues in that bulletin. OEM and carrier-provided updates should also be applied where applicable.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleAndroidoperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity3

Community discussion across Reddit, Mastodon, and other social sources.