dbcve.org
AndroidOperating system · Google

CVE-2025-22435

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 avdt_msg_ind of avdt_msg.cc, there is a possible memory corruption due to type confusion. This could lead to paired device escalation of privilege 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 · high confidence

A type confusion vulnerability in the AVDT (Audio/Video Distribution Transport Protocol) message handler (avdt_msg.cc) in Android's Bluetooth stack allows a paired Bluetooth device to cause memory corruption and escalate privileges without any user interaction.

MitigationApply vendor-provided Android security patches addressing CVE-2025-22435 immediately; ensure Bluetooth is disabled when not in use as a defense-in-depth measure until the patch is applied.

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Check Android OS version
    Go to Settings > About Phone > Android version, or run `getprop ro.build.version.release` in ADB shell
    Affected if The version shown is 13.0, 14.0, or 15.0 exactly
  2. Verify Bluetooth is enabled
    Go to Settings > Bluetooth and confirm it is turned on, or run `settings get global bluetooth_on` in ADB shell (returns 1 if enabled)
    Affected if Bluetooth is currently enabled (value is 1)
  3. Check for paired Bluetooth devices
    Go to Settings > Bluetooth > Paired devices, or run `bluetoothctl paired-devices` in ADB shell
    Affected if One or more devices are paired - the attacker needs an already-paired device to trigger the AVDT flaw
  4. Confirm AVDT audio profiles are active
    Check if Bluetooth audio (A2DP) or AV remote control (AVRCP) has been used recently - this indicates the AVDT message handler is processing data. On a rooted device, check `dumpsys bluetooth_manager` for AVDT connection info
    Affected if Any AVDT-based Bluetooth audio connection has been established since the last device restart

If the Android version is exactly 13.0, 14.0, or 15.0 AND Bluetooth is enabled with paired devices, the device is potentially affected by this type confusion vulnerability in the AVDT message handler.

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

Apply vendor-provided Android security patches addressing CVE-2025-22435 immediately; ensure Bluetooth is disabled when not in use as a defense-in-depth measure until the patch is applied.

Recommended fix Moderate confidence

Latest available Android security patch update for your device model (Android 13.0/14.0/15.0 with latest Security Patch Level)

  1. Check your device's current Android version and Security Patch Level in Settings > About Phone > Android version
  2. Verify if your device manufacturer has released a security update for Android 13.0, 14.0, or 15.0 that addresses CVE-2025-22435
  3. If a security update is available, install it through Settings > System > Software Update > Check for updates
  4. For devices that no longer receive monthly security updates, consider upgrading to a device that currently receives active security support from the manufacturer
  5. Alternatively, as a mitigation, avoid pairing with untrusted Bluetooth devices to reduce the attack surface for this vulnerability
Caveat Standard Android security update risks apply - review release notes for your specific device model before applying

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
38.0 hours of engineering $6,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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