Name: DOCSIS infinite loop
Date: July 18, 2017
Affected versions: 2.2.0 to 2.2.7, 2.0.0 to 2.0.13
Fixed versions: 2.2.8, 2.0.14
The DOCSIS 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 2.2.8, 2.0.14 or later.