From: Sasha Levin <sashal@kernel.org>
To: Ben Hutchings <ben.hutchings@codethink.co.uk>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <Alexander.Levin@microsoft.com>,
stable <stable@vger.kernel.org>
Subject: Re: Security fixes for 4.14
Date: Sun, 2 Dec 2018 09:54:23 -0500 [thread overview]
Message-ID: <20181202145423.GF221015@sasha-vm> (raw)
In-Reply-To: <1543530471.2867.12.camel@codethink.co.uk>
On Thu, Nov 29, 2018 at 10:27:51PM +0000, Ben Hutchings wrote:
>I've backported a number of fixes for security issues affecting 4.14-
>stable. All of these are already fixed in 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 didn't regress and
>temporarily added logging to check that the mitigation is applied when
>needed.
Queued for 4.14, thank you.
--
Thanks,
Sasha
prev parent reply other threads:[~2018-12-02 14:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 22:27 Security fixes for 4.14 Ben Hutchings
2018-12-02 14:54 ` Sasha Levin [this message]
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=20181202145423.GF221015@sasha-vm \
--to=sashal@kernel.org \
--cc=Alexander.Levin@microsoft.com \
--cc=ben.hutchings@codethink.co.uk \
--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