Adjacent device crash via Bluetooth buffer underflow
Published Jul 8, 2025 · Updated Jul 14, 2025
Buffer underflow in MediaTek Bluetooth firmware on listed chipsets allows physically proximate attackers to crash affected devices. The bulletin states that a buffer underwrite causes an uncaught exception in the firmware, but it publishes no function or input path. Bluetooth proximity is required, but authentication, prior privileges, and user interaction are not; the reported consequence is a device crash only.
Summary
What happened
Buffer underflow in MediaTek Bluetooth firmware on listed chipsets allows physically proximate attackers to crash affected devices. The bulletin states that a buffer underwrite causes an uncaught exception in the firmware, but it publishes no function or input path. Bluetooth proximity is required, but authentication, prior privileges, and user interaction are not; the reported consequence is a device crash only.
The record
- CVE
- CVE-2025-20695
- Published
- Jul 8, 2025
- Updated
- Jul 14, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-124, CWE-787, 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