CVE-2018-11806

Description

m_cat in slirp/mbuf.c in Qemu has a heap-based buffer overflow via incoming fragmented datagrams.

Link	Tags
https://access.redhat.com/errata/RHSA-2018:2762	third party advisory vendor advisory
http://www.securityfocus.com/bid/104400	vdb entry third party advisory
https://usn.ubuntu.com/3826-1/	third party advisory vendor advisory
https://lists.gnu.org/archive/html/qemu-devel/2018-06/msg01012.html	third party advisory mailing list
http://www.openwall.com/lists/oss-security/2018/06/07/1	third party advisory mailing list
https://bugzilla.redhat.com/show_bug.cgi?id=1586245	issue tracking third party advisory patch
https://www.zerodayinitiative.com/advisories/ZDI-18-567/	vdb entry third party advisory
https://access.redhat.com/errata/RHSA-2018:2462	third party advisory vendor advisory
https://access.redhat.com/errata/RHSA-2018:2822	third party advisory vendor advisory
https://access.redhat.com/errata/RHSA-2018:2887	third party advisory vendor advisory
https://lists.debian.org/debian-lts-announce/2019/05/msg00010.html	third party advisory mailing list
https://www.debian.org/security/2019/dsa-4454	third party advisory vendor advisory
https://seclists.org/bugtraq/2019/May/76	third party advisory mailing list
https://access.redhat.com/errata/RHSA-2019:2892	third party advisory vendor advisory

What is the severity of CVE-2018-11806?: CVE-2018-11806 has been scored as a high severity vulnerability.
How to fix CVE-2018-11806?: To fix CVE-2018-11806, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2018-11806 being actively exploited in the wild?: As for now, there are no information to confirm that CVE-2018-11806 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.