{"id":"CVE-2019-5611","url":"https://www.cyber-defence.io/tools/cve/CVE-2019-5611","generatedAt":"2026-10-27T22:24:39.713Z","title":"In FreeBSD 12.0-STABLE before r350828, 12.0-RELEASE before 12.0-RELEASE-p10, 11.3-STABLE before r350829, 11.3-RELEASE before 11.3-RELEASE-p3, and 11.2-RELEASE before 11.2-RELEASE-p14, a missing check in the function to arrange data in a chain of mbufs…","description":"In FreeBSD 12.0-STABLE before r350828, 12.0-RELEASE before 12.0-RELEASE-p10, 11.3-STABLE before r350829, 11.3-RELEASE before 11.3-RELEASE-p3, and 11.2-RELEASE before 11.2-RELEASE-p14, a missing check in the function to arrange data in a chain of mbufs could cause data returned not to be contiguous. Extra checks in the IPv6 stack could catch the error condition and trigger a kernel panic, leading to a remote denial of service.","published":"2019-08-30T09:15:21.000Z","lastModified":"2026-06-17T02:37:56.000Z","status":"Modified","sourceIdentifier":"secteam@freebsd.org","cvss":{"version":"3.1","score":7.5,"severity":"HIGH","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"},"cwe":["CWE-20"],"affected":["freebsd/freebsd","netapp/clustered data ontap"],"epss":{"score":0.04417,"percentile":0.91283,"date":"2026-10-26","history":[]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"high","text":"High impact if exploited, but EPSS currently rates exploitation as unlikely (4.42%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit."},"changes":[],"references":[{"url":"http://packetstormsecurity.com/files/154170/FreeBSD-Security-Advisory-FreeBSD-SA-19-22.mbuf.html","tags":["Exploit","Patch","Third Party Advisory","VDB Entry"],"source":"secteam@freebsd.org"},{"url":"https://seclists.org/bugtraq/2019/Aug/33","tags":["Exploit","Mailing List","Patch","Third Party Advisory"],"source":"secteam@freebsd.org"},{"url":"https://security.FreeBSD.org/advisories/FreeBSD-SA-19:22.mbuf.asc","tags":["Patch","Vendor Advisory"],"source":"secteam@freebsd.org"},{"url":"https://security.FreeBSD.org/advisories/FreeBSD-SA-19:22.mbuf.asc","tags":["Patch","Vendor Advisory"],"source":"secteam@freebsd.org"},{"url":"https://security.FreeBSD.org/advisories/FreeBSD-SA-19:22.mbuf.asc","tags":["Patch","Vendor Advisory"],"source":"secteam@freebsd.org"},{"url":"https://security.FreeBSD.org/advisories/FreeBSD-SA-19:22.mbuf.asc","tags":["Patch","Vendor Advisory"],"source":"secteam@freebsd.org"},{"url":"https://security.netapp.com/advisory/ntap-20190910-0002/","tags":["Third Party Advisory"],"source":"secteam@freebsd.org"},{"url":"http://packetstormsecurity.com/files/154170/FreeBSD-Security-Advisory-FreeBSD-SA-19-22.mbuf.html","tags":["Exploit","Patch","Third Party Advisory","VDB Entry"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://seclists.org/bugtraq/2019/Aug/33","tags":["Exploit","Mailing List","Patch","Third Party Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://security.FreeBSD.org/advisories/FreeBSD-SA-19:22.mbuf.asc","tags":["Patch","Vendor Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://security.FreeBSD.org/advisories/FreeBSD-SA-19:22.mbuf.asc","tags":["Patch","Vendor Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://security.FreeBSD.org/advisories/FreeBSD-SA-19:22.mbuf.asc","tags":["Patch","Vendor Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://security.FreeBSD.org/advisories/FreeBSD-SA-19:22.mbuf.asc","tags":["Patch","Vendor Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://security.netapp.com/advisory/ntap-20190910-0002/","tags":["Third Party Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2019-5611","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}