libpcap before 1.9.1, as used in tcpdump before 4.9.3, has a buffer overflow and/or over-read because of errors in pcapng reading. References: https://github.com/the-tcpdump-group/libpcap/blob/libpcap-1.9/CHANGES
Created libpcap tracking bugs for this issue: Affects: fedora-all [bug 1760624]
According to upstream (see comments after https://github.com/the-tcpdump-group/libpcap/issues/855#issuecomment-575450988) this is not a real issue in libpcap, so I'm closing this as NOTABUG.
Following the discussion on https://github.com/the-tcpdump-group/libpcap/issues/855, I'm turning this bug into a security issue for tcpdump (instead of libpcap). Upstream fix: https://github.com/the-tcpdump-group/tcpdump/commit/faf8fb7 [master] https://github.com/the-tcpdump-group/tcpdump/commit/8ab211a [4.9]