Adjacent device crash via Bluetooth firmware underflow
Published Jul 8, 2025 · Updated Jul 14, 2025
Buffer underflow in MediaTek Bluetooth firmware allows physically proximate attackers to crash affected Android and OpenWrt devices. The vendor identifies a buffer underflow that raises an uncaught exception but has not disclosed the affected routine or triggering input. No credentials or user interaction are required, and successful exploitation interrupts availability by crashing the device; confidentiality and integrity are unaffected.
Summary
What happened
Buffer underflow in MediaTek Bluetooth firmware allows physically proximate attackers to crash affected Android and OpenWrt devices. The vendor identifies a buffer underflow that raises an uncaught exception but has not disclosed the affected routine or triggering input. No credentials or user interaction are required, and successful exploitation interrupts availability by crashing the device; confidentiality and integrity are unaffected.
The record
- CVE
- CVE-2025-20694
- Published
- Jul 8, 2025
- Updated
- Jul 14, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-124, T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 8, 2025CVE publishedPublication date reported by the CVE source.
- Jul 14, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo