dbcve.org
Software Development KitApplication · Mediatek

CVE-2025-20695

MEDIUM · 6.5 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to after 3.7 or later.
See remediation →
70/100
Remediation priority · Elevated
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 Bluetooth FW, there is a possible system crash due to an uncaught exception. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS09741871; Issue ID: MSV-3317.

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

This is a Bluetooth firmware vulnerability where an uncaught exception triggers a system crash, leading to remote denial of service. The attack can be carried out without requiring any additional privileges or user interaction, making it a relatively simple DoS vector against affected devices.

MitigationApply the vendor firmware patch (ALPS09741871) once available. Until the patch is released, consider reducing Bluetooth exposure through network segmentation or disabling Bluetooth on non-essential devices.

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
Software Development KitApplication
Affected:<= 3.7
AndroidOperating system
Affected:= 13.0= 14.0= 15.0
OpenwrtOperating system
Affected:= 21.02.0= 23.05

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

CVSS:3.1/AV:A/AC:L/PR:N/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. Identify your device platform
    Determine if your device runs Mediatek SDK, Google Android, or OpenWRT firmware. This is typically visible in your device settings, system information, or product documentation.
    Affected if Device uses Mediatek SDK, Android 13.0/14.0/15.0, or OpenWRT 21.02.0/23.05
  2. Check Mediatek SDK version
    For Mediatek-based devices, run 'cat /proc/mediatek/version' or check the SDK documentation/package metadata to find the SDK version number.
    Affected if SDK version is 3.7 or lower
  3. Check Android version
    On Android devices, go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB.
    Affected if Android version is exactly 13.0, 14.0, or 15.0
  4. Check OpenWRT version
    Run 'cat /etc/openwrt_version' or 'cat /etc/os-release' to identify the installed OpenWRT release version.
    Affected if OpenWRT version is exactly 21.02.0 or 23.05
  5. Verify Bluetooth is enabled
    Check if Bluetooth is powered on. On Android: Settings > Bluetooth or run 'settings get global bluetooth_on'. On Linux/OpenWRT: run 'hciconfig' or check 'rfkill list bluetooth'.
    Affected if Bluetooth interface is active and powered on

You are affected if your device runs Mediatek SDK <= 3.7, Android 13.0/14.0/15.0, or OpenWRT 21.02.0/23.05 AND has Bluetooth enabled.

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
Upgrade available Upgrade to a release after 3.7
Interim mitigation

Apply the vendor firmware patch (ALPS09741871) once available. Until the patch is released, consider reducing Bluetooth exposure through network segmentation or disabling Bluetooth on non-essential devices.

Recommended fix Moderate confidence
  1. 1. Identify the MediaTek device or product containing the affected Bluetooth firmware
  2. 2. Contact the device manufacturer (OEM/ODM) to request the firmware update containing patch ALPS09741871
  3. 3. Apply the manufacturer-provided firmware update through the standard OTA or manual firmware flashing process provided by the device vendor
  4. 4. Verify the Bluetooth firmware has been updated to a version containing the security fix
Caveat Firmware updates may require device downtime and should be tested in a staging environment before production deployment; contact manufacturer for specific update procedures

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

Fix this in Software Development Kit Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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