CVE-2026-76922 is a denial-of-service vulnerability in Wireshark's Bluetooth BR/EDR RF dissector affecting Wireshark 4.6.0 through 4.6.7 and 4.4.0 through 4.4.18. The dissector declares an L2CAP reassembly table but fails to register it. When it processes a truncated initial fragment of an L2CAP message, it invokes fragment_add_seq_next() with the unregistered table, whose callbacks are NULL. This produces a NULL control-flow dereference and crashes Wireshark or TShark during dissection of crafted fragmented Bluetooth BR/EDR L2CAP traffic.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A denial-of-service crash in the Wireshark Bluetooth BR/EDR FHS protocol dissector.
A Wireshark vulnerability addressed by Debian DSA-6471; the advisory states the set of flaws could cause denial of service or arbitrary-code execution.
A specific vulnerability identified as CVE-2026-76922, referenced in a Nessus plugin as unpatched and associated with Debian Linux and the wireshark package.
A denial-of-service vulnerability in Wireshark/TShark's Bluetooth BR/EDR RF dissector where an unregistered L2CAP reassembly table leads to a NULL callback dereference and crash when parsing crafted fragmented L2CAP traffic.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.