CVE-2025-20694
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 · uneditedIn 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: ALPS09752821; Issue ID: MSV-3342.
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 confidenceA denial of service vulnerability exists in Bluetooth firmware where an uncaught exception causes system crash. The issue is triggerable remotely without requiring any user interaction or elevated privileges, indicating the exception handler is missing for a specific Bluetooth protocol message or state condition.
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<= 3.7= 13.0= 14.0= 15.0= 21.02.0= 23.05CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device platform and software stackDetermine if the system uses Mediatek Bluetooth firmware, Android OS, or OpenWrt. For embedded devices, check the manufacturer and firmware documentation to identify the Bluetooth chipset and software components.Affected if The device uses Mediatek SDK, Android, or OpenWrt as listed in affected products
-
Check Mediatek SDK versionIf using Mediatek-based Bluetooth firmware, locate the SDK version file (typically in /system/etc/firmware or via 'getprop' on Android, or check the SDK release notes). Run: getprop | grep mediatek or check /vendor/etc/build.prop for version entries.Affected if SDK version is 3.7 or lower (any version <= 3.7)
-
Check Android OS versionOn Android devices, go to Settings > About Phone > Android version, or run: getprop ro.build.version.releaseAffected if Android version is exactly 13.0, 14.0, or 15.0
-
Check OpenWrt versionOn OpenWrt devices, run: cat /etc/os-release or check the luci interface System > Overview page for the firmware version.Affected if OpenWrt version is exactly 21.02.0 or 23.05
-
Verify Bluetooth is enabledCheck if Bluetooth is active on the device. On Android: Settings > Bluetooth (ensure toggle is on). On Linux/OpenWrt: run 'rfkill list' or 'hciconfig' to check Bluetooth adapter status.Affected if Bluetooth is enabled and the device matches the affected version criteria
The environment is affected if it runs Mediatek SDK <= 3.7, Android 13.0/14.0/15.0, or OpenWrt 21.02.0/23.05 AND has Bluetooth functionality enabled, as the missing exception handler can be triggered remotely.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply the vendor firmware patch (ALPS09752821) to affected devices. Since this is a firmware-level fix, ensure proper testing of Bluetooth functionality after deployment to verify the exception handler is correctly implemented and doesn't introduce regressions.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20694 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-20694 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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