From: Greg KH <gregkh@linuxfoundation.org>
To: Zubin Mithra <zsm@chromium.org>
Cc: stable@vger.kernel.org, groeck@chromium.org,
blackgod016574@gmail.com, davem@davemloft.net,
kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org
Subject: Re: 95baa60a0da8 ("ipv6_sockglue: Fix a missing-check bug in ip6_ra_control()")
Date: Tue, 4 Jun 2019 10:04:05 +0200 [thread overview]
Message-ID: <20190604080405.GA3779@kroah.com> (raw)
In-Reply-To: <20190604075235.GD6840@kroah.com>
On Tue, Jun 04, 2019 at 09:52:35AM +0200, Greg KH wrote:
> On Mon, Jun 03, 2019 at 10:31:15AM -0700, Zubin Mithra wrote:
> > Hello,
> >
> > CVE-2019-12378 was fixed in the upstream linux kernel with the following commit.
> > * 95baa60a0da8 ("ipv6_sockglue: Fix a missing-check bug in ip6_ra_control()")
>
> A CVE was created for that tiny thing?
>
> Hah, no, I think I'll refuse to apply it just for the very point of it.
> That's something that can not be triggered by normal operations, right?
> It's a bugfix-for-the-theoritical from what I can see...
>
> > Could the patch be applied to v4.19.y, v4.14.y, v4.9.y and v4.4.y?
>
> Why are you ignoring 5.1?
Also, stable networking patches need to come from the networking
maintainer, as the documentation states, so I shouldn't be applying this
directly anyway. If Dave thinks it is worth to backport, I'll gladly
apply it from his submissions, so you need to convince him, not me.
thanks,
greg k-h
next prev parent reply other threads:[~2019-06-04 8:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 17:31 95baa60a0da8 ("ipv6_sockglue: Fix a missing-check bug in ip6_ra_control()") Zubin Mithra
2019-06-04 7:52 ` Greg KH
2019-06-04 8:04 ` Greg KH [this message]
2019-06-04 8:43 ` Guenter Roeck
2019-06-04 9:04 ` 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=20190604080405.GA3779@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=blackgod016574@gmail.com \
--cc=davem@davemloft.net \
--cc=groeck@chromium.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=stable@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.org \
--cc=zsm@chromium.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.