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>
Subject: Re: Security fixes for 4.9
Date: Thu, 6 Dec 2018 15:28:38 +0100 [thread overview]
Message-ID: <20181206142838.GA9060@kroah.com> (raw)
In-Reply-To: <1544105974.2867.66.camel@codethink.co.uk>
On Thu, Dec 06, 2018 at 02:19:34PM +0000, Ben Hutchings wrote:
> I've backported a number of fixes for security issues affecting 4.9-
> stable.��All of these are already fixed in 4.14-stable and 4.19-stable.
>
> Most of the issues involve filesystem validation, and I tested with the
> reproducers where available.
>
> For the BPF fix, I verified that the self-tests (taken from 4.14)
> didn't regress and temporarily added logging to check that the
> mitigation is applied when needed.
Many thanks for tehse all now queued up.
greg k-h
next prev parent reply other threads:[~2018-12-06 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 14:19 Security fixes for 4.9 Ben Hutchings
2018-12-06 14:28 ` Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-15 16:55 Ben Hutchings
2017-11-15 18:00 ` Greg Kroah-Hartman
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=20181206142838.GA9060@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Alexander.Levin@microsoft.com \
--cc=ben.hutchings@codethink.co.uk \
--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.