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. Upstream bug: https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14080 Upstream patch: https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=625bab309d9dd21db2d8ae2aa3511810d32842a8 External References: https://www.wireshark.org/security/wnpa-sec-2017-46.html
Created wireshark tracking bugs for this issue: Affects: fedora-all [bug 1500769]