Denial of service via unregistered reassembly table
Published Aug 19, 2026 · Updated Aug 20, 2026
Denial of service in Wireshark before 4.6.8 and 4.4.18 allows attackers to crash the application via crafted Bluetooth BR/EDR traffic. In the BT BR/EDR RF dissector, dissect_btbredr_rf() passes l2cap_msg_reassembly_table to fragment_add_seq_next() even though the table is never registered, leaving NULL callbacks when truncated L2CAP start fragments trigger reassembly. Reachability requires valid BR/EDR connection state and either injected malformed traffic or a crafted capture file, so the consequence is an analyzer crash rather than packet tampering or code execution.
Summary
What happened
Denial of service in Wireshark before 4.6.8 and 4.4.18 allows attackers to crash the application via crafted Bluetooth BR/EDR traffic. In the BT BR/EDR RF dissector, dissect_btbredr_rf() passes l2cap_msg_reassembly_table to fragment_add_seq_next() even though the table is never registered, leaving NULL callbacks when truncated L2CAP start fragments trigger reassembly. Reachability requires valid BR/EDR connection state and either injected malformed traffic or a crafted capture file, so the consequence is an analyzer crash rather than packet tampering or code execution.
The record
- CVE
- CVE-2026-76922
- Published
- Aug 19, 2026
- Updated
- Aug 20, 2026
- Vendor
- Wireshark Foundation
- Product
- Wireshark
- Classifications
- CWE-476
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 19, 2026CVE publishedPublication date reported by the CVE source.
- Aug 20, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.4.0 <4.4.18
- Affected versionversion=4.6.0 <4.6.8
What conditions does exploitation require?
What is affected?
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
- poc.py and crash.pcap proof of conceptproof of concept · demonstrated
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