Name: Profinet I/O long loop
Date: November 16, 2016
Affected versions: 2.2.0 to 2.2.1
Fixed versions: 2.2.2
The Profinet I/O dissector could loop excessively.
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.2 or later.