From: Greg KH <gregkh@linuxfoundation.org>
To: Juerg Haefliger <juerg.haefliger@hpe.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 4.4 0/5] CVE fixes for stable 4.4
Date: Wed, 26 Oct 2016 17:36:32 +0200 [thread overview]
Message-ID: <20161026153632.GA27371@kroah.com> (raw)
In-Reply-To: <20161026150036.3172-1-juerg.haefliger@hpe.com>
On Wed, Oct 26, 2016 at 05:00:31PM +0200, Juerg Haefliger wrote:
> This series fixes the following CVEs:
> 1/5: CVE-2016-8658
> 2/5: CVE-2016-7097
> 4/5: CVE-2016-8666
>
> 3-5 is a patch series that also fixes a performance issue with GRO
> encapsulation.
Thanks for these, I'll apply them in the next round of kernels after
this one.
Just curious, why all of the interest in the 4.4-stable kernel tree?
I'm not complaining, as it is really helpful...
thanks,
greg k-h
next prev parent reply other threads:[~2016-10-26 15:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 15:00 [PATCH 4.4 0/5] CVE fixes for stable 4.4 Juerg Haefliger
2016-10-26 15:00 ` [PATCH 4.4 1/5] brcmfmac: avoid potential stack overflow in brcmf_cfg80211_start_ap() Juerg Haefliger
2016-10-26 15:00 ` [PATCH 4.4 2/5] posix_acl: Clear SGID bit when setting file permissions Juerg Haefliger
2016-10-26 15:00 ` [PATCH 4.4 3/5] ipip: Properly mark ipip GRO packets as encapsulated Juerg Haefliger
2016-10-26 15:00 ` [PATCH 4.4 4/5] tunnels: Don't apply GRO to multiple layers of encapsulation Juerg Haefliger
2016-10-26 15:00 ` [PATCH 4.4 5/5] tunnels: Remove encapsulation offloads on decap Juerg Haefliger
2016-10-26 15:36 ` Greg KH [this message]
2016-10-26 17:14 ` [PATCH 4.4 0/5] CVE fixes for stable 4.4 Juerg Haefliger
2016-10-28 15:48 ` Greg KH
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=20161026153632.GA27371@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=juerg.haefliger@hpe.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.