From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable <stable@vger.kernel.org>
Subject: Re: Please apply dd83c161fbcc ("kernel/exit.c: avoid undefined behaviour when calling wait4()") to v4.9.y and older
Date: Sat, 19 May 2018 09:44:54 +0200 [thread overview]
Message-ID: <20180519074454.GA5925@kroah.com> (raw)
In-Reply-To: <20180518160007.GA5123@roeck-us.net>
On Fri, May 18, 2018 at 09:00:07AM -0700, Guenter Roeck wrote:
> On Fri, May 18, 2018 at 04:52:07PM +0200, Greg Kroah-Hartman wrote:
> > On Fri, May 18, 2018 at 06:47:46AM -0700, Guenter Roeck wrote:
> > > Hi Greg,
> > >
> > > please apply commit dd83c161fbc ("kernel/exit.c: avoid undefined behaviour when calling wait4()")
> > > to v4.9.y and older to fix CVE-2018-10087.
> >
> > Odd no one asked for that one to be backported before :(
> >
>
> Not entirely surprising. The patch is from July 2017, it wasn't marked
> for stable, and the CVE has been created only recently (04/13/2018).
> CVE severity and the reference to the upstream commit were added
> yesterday, which caused our CVE tracker to barf at me.
Who applied for the CVE number? They should have been the ones to
notify people of the issue, so who should I go kick about this? :)
thanks,
greg k-h
next prev parent reply other threads:[~2018-05-19 7:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 13:47 Please apply dd83c161fbcc ("kernel/exit.c: avoid undefined behaviour when calling wait4()") to v4.9.y and older Guenter Roeck
2018-05-18 14:52 ` Greg Kroah-Hartman
2018-05-18 16:00 ` Guenter Roeck
2018-05-19 7:44 ` Greg Kroah-Hartman [this message]
2018-05-19 14:09 ` Guenter Roeck
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=20180519074454.GA5925@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux@roeck-us.net \
--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