Device crash via crafted L2CAP packet
Published Sep 8, 2026 · Updated Sep 8, 2026
Heap overflow in Bestechnic BES2300 firmware 3.x and earlier allows remote attackers to crash devices with a crafted L2CAP packet. The A2DP SBC packet path passes attacker-controlled frame data into the decoder, where processing overruns a heap buffer; the specific missing bounds check is undisclosed. Unauthenticated Bluetooth packet delivery is required, and the documented consequence is a service-interrupting device crash rather than data disclosure or modification.
Summary
What happened
Heap overflow in Bestechnic BES2300 firmware 3.x and earlier allows remote attackers to crash devices with a crafted L2CAP packet. The A2DP SBC packet path passes attacker-controlled frame data into the decoder, where processing overruns a heap buffer; the specific missing bounds check is undisclosed. Unauthenticated Bluetooth packet delivery is required, and the documented consequence is a service-interrupting device crash rather than data disclosure or modification.
The record
- CVE
- CVE-2026-79377
- Published
- Sep 8, 2026
- Updated
- Sep 8, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-122, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 8, 2026CVE publishedPublication date reported by the CVE source.
- Sep 8, 2026Record 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