stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <ben.hutchings@codethink.co.uk>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Sasha Levin <Alexander.Levin@microsoft.com>
Cc: stable <stable@vger.kernel.org>,
	Eric Dumazet <edumazet@google.com>,
	Peter Oskolkov <posk@google.com>
Subject: [4.4] FragmentSmack security fixes
Date: Tue, 05 Feb 2019 18:26:23 +0000	[thread overview]
Message-ID: <1549391183.2925.179.camel@codethink.co.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 612 bytes --]

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.

Ben.

-- 
Ben Hutchings, Software Developer                         Codethink Ltd
https://www.codethink.co.uk/                 Dale House, 35 Dale Street
                                     Manchester, M1 2HF, United Kingdom

[-- Attachment #2: security-4.4-fragmentsmack.mbox --]
[-- Type: application/mbox, Size: 175807 bytes --]

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05 18:26 Ben Hutchings [this message]
2019-02-05 18:41 ` [4.4] FragmentSmack security fixes Greg Kroah-Hartman
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=1549391183.2925.179.camel@codethink.co.uk \
    --to=ben.hutchings@codethink.co.uk \
    --cc=Alexander.Levin@microsoft.com \
    --cc=edumazet@google.com \
    --cc=gregkh@linuxfoundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).