All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ben Hutchings <ben.hutchings@codethink.co.uk>
Cc: Sasha Levin <Alexander.Levin@microsoft.com>,
	stable <stable@vger.kernel.org>,
	Eric Dumazet <edumazet@google.com>,
	Peter Oskolkov <posk@google.com>
Subject: Re: [4.4] FragmentSmack security fixes
Date: Tue, 5 Feb 2019 19:41:05 +0100	[thread overview]
Message-ID: <20190205184105.GA22198@kroah.com> (raw)
In-Reply-To: <1549391183.2925.179.camel@codethink.co.uk>

On Tue, Feb 05, 2019 at 06:26:23PM +0000, Ben Hutchings wrote:
> This is a backport of upstream changes to fix the FragmentSmack (CVE-
> 2018-5391) vulnerability.
> 
> Peter Oskolkov checked an earlier version of this backport, but I have
> since rebased and added another 3 commits to it.  I tested with the
> ip_defrag.sh self-test that he added upstream, and it passed.  I have
> included the fix that is currently queued for the 4.9, 4.14 and 4.19
> branches.

That's a lot of patches, some of which I have already queued up in the
next 4.4 release which will happen in a day or so.  Are they all still
needed after the changes there are merged?

thanks,

greg k-h

  reply	other threads:[~2019-02-05 18:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05 18:26 [4.4] FragmentSmack security fixes Ben Hutchings
2019-02-05 18:41 ` Greg Kroah-Hartman [this message]
2019-02-05 19:41   ` Ben Hutchings
2019-02-06 21:13     ` Greg Kroah-Hartman
2019-02-07 11:26       ` Greg Kroah-Hartman
2019-02-09  1:58         ` maowenan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190205184105.GA22198@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Alexander.Levin@microsoft.com \
    --cc=ben.hutchings@codethink.co.uk \
    --cc=edumazet@google.com \
    --cc=posk@google.com \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.