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.
Created wireshark tracking bugs for this issue:
Affects: fedora-all [bug 1697953]
This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 8 as they did not include support for Ruby Marshal Object (RBM).
An infinite loop in the Rbm dissector is possible when a malformed packet is read on the wire or analyzed from a trace file.