Name: IEEE 802.11 dissector infinite loop
Date: April 8, 2019
Affected versions: 3.0.0
Fixed versions: 3.0.1
The IEEE 802.11 dissector could go into an infinite loop.
It may be possible to make Wireshark consume excessive CPU resources by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file.
Upgrade to Wireshark 3.0.1 or later.