Date: Tue, 18 Sep 2018 17:48:26 -0400 From: Ryan Stone <rysto32@gmail.com> To: freebsd-net <freebsd-net@freebsd.org> Subject: Fwd: Status of 10.4 fixes for CVE-2018-6923 (Fragment Stack) Message-ID: <CAFMmRNytdufmR%2BBcE02fhuOXnv_BH=VgcVPTPA2LGQxFM9V=4w@mail.gmail.com> In-Reply-To: <CAFMmRNxtHU7bAZ=yhDtVitkMUanr0=jVAQowPShoSxEQgUZ-zA@mail.gmail.com> References: <CAFMmRNxtHU7bAZ=yhDtVitkMUanr0=jVAQowPShoSxEQgUZ-zA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I didn't get a response to this, so I'm forwarding to a higher-traffic list. Does anybody know if there is work in progress on a for for stable/10? ---------- Forwarded message --------- From: Ryan Stone <rysto32@gmail.com> Date: Tue, Sep 11, 2018 at 2:37 PM Subject: Status of 10.4 fixes for CVE-2018-6923 (Fragment Stack) To: <freebsd-transport@freebsd.org> <freebsd-transport@freebsd.org> In the security advisory for CVE-2018-6923, it says that fixes for 10.4 are forthcoming. They don't seem to have landed in the tree yet. We're going to need to ship a 10.x fix for $WORK and I'd like to know if we need to implement the fix ourselves or if the patch is in the works already. Thanks, Ryan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFMmRNytdufmR%2BBcE02fhuOXnv_BH=VgcVPTPA2LGQxFM9V=4w>