public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Jack Wang <jinpuwang@gmail.com>
To: gregkh@linuxfoundation.org, stable@vger.kernel.org
Subject: [stable-4.9 && 4.14 0/2] CVE 2018-1000026 fixes
Date: Thu, 14 Feb 2019 11:31:16 +0100	[thread overview]
Message-ID: <20190214103118.4350-1-jinpuwang@gmail.com> (raw)

Hi Greg,

This is clean cherry-pick from upstream 4.16 for CVE 2018-1000026

Other OS vendors have the fixes in their kernels[1][2], but not yet in upstream
stable tree for 4.9 and 4.14.

Compile tested with 4.14.93.

Please consider to include them.

Thanks,
Jack Wang

Linux Kernel Developer @ 1&1 IONOS Cloud GmbH

[1] https://bugs.launchpad.net/bugs/cve/2018-1000026
[2] https://access.redhat.com/security/cve/cve-2018-1000026


Daniel Axtens (2):
  net: create skb_gso_validate_mac_len()
  bnx2x: disable GSO where gso_size is too big for hardware

 .../net/ethernet/broadcom/bnx2x/bnx2x_main.c  | 18 ++++++
 include/linux/skbuff.h                        | 16 +++++
 net/core/skbuff.c                             | 63 +++++++++++++++----
 net/sched/sch_tbf.c                           | 10 ---
 4 files changed, 84 insertions(+), 23 deletions(-)

-- 
2.17.1


             reply	other threads:[~2019-02-14 10:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-14 10:31 Jack Wang [this message]
2019-02-14 10:31 ` [stable-4.9 && 4.14 1/2] net: create skb_gso_validate_mac_len() Jack Wang
2019-02-14 10:31 ` [stable-4.9 && 4.14 2/2] bnx2x: disable GSO where gso_size is too big for hardware Jack Wang
2019-02-17 19:26 ` [stable-4.9 && 4.14 0/2] CVE 2018-1000026 fixes Sasha Levin

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=20190214103118.4350-1-jinpuwang@gmail.com \
    --to=jinpuwang@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --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