Name: DOCSIS infinite loop
Date: October 10, 2017
Affected versions: 2.4.0 to 2.4.1
Fixed versions: 2.4.2
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.4.2 or later.