dbcve.org
AndroidOperating system · Google

CVE-2025-22431

MEDIUM · 5.5 CVSS v3.1 Published 2025-09-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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 multiple locations, there is a possible method for a malicious app to prevent dialing emergency services under limited circumstances due to a logic error in the code. This could lead to local denial of service until the phone reboots 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

A logic error in multiple locations within the Android telephony system allows a malicious local application to prevent the device from dialing emergency services. The denial of service persists until the device reboots, and exploitation requires no special privileges or user interaction.

MitigationApplication developers should ensure proper permission handling and state management in emergency calling code paths. End users should update to the latest Android security patch level once available.

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:= 13.0= 14.0= 15.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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Confirm Android version
    Go to Settings > About Phone > Android version (or run 'getprop ro.build.version.release' via ADB)
    Affected if Version is exactly 13.0, 14.0, or 15.0 (not a later patch version)
  2. Check for unknown or suspicious applications
    Review installed apps in Settings > Apps, looking for unfamiliar apps with telephony or accessibility permissions that were installed without user action
    Affected if Unknown apps with unusual permissions are present, especially those with phone or call log access that the user did not intentionally install
  3. Verify emergency calling functionality
    Check if the Phone app can still initiate calls to emergency numbers (do not actually place an emergency call as a test - verify the UI allows dialer input to 112/911 etc)
    Affected if The dialer fails to initiate emergency numbers, shows no response, or displays an error when attempting to dial emergency numbers
  4. Inspect telephony service state
    Run 'dumpsys telephony.registry' via ADB to check the telephony registration state and service state fields
    Affected if Service state shows as 'in service' but emergency calls are not registerable or the registry shows abnormal state flags

You are likely affected if your Android version is exactly 13.0, 14.0, or 15.0 and emergency calling is non-functional or blocked.

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

Application developers should ensure proper permission handling and state management in emergency calling code paths. End users should update to the latest Android security patch level once available.

Recommended fix Moderate confidence

Android Security Patch Level March 2025 or later

  1. 1. Check your device's current Android security patch level in Settings > About Phone > Android version
  2. 2. Apply the latest Android security update for your device model
  3. 3. For Android 13.0, 14.0, and 15.0 devices, ensure the March 2025 or later security patch level is installed
  4. 4. If the update is not available from your device manufacturer, consider upgrading to a device model that receives active security support
Caveat Security updates typically have no breaking changes; they only contain bug and vulnerability fixes

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22431 — 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-22431 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