All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jason Yan <yanaijie@huawei.com>
Cc: daniel@iogearbox.net, Jann Horn <jannh@google.com>,
	ast@kernel.org, "zhangyi (F)" <yi.zhang@huawei.com>,
	Zhaohongjiang <zhaohongjiang@huawei.com>,
	netdev@vger.kernel.org, stable@vger.kernel.org
Subject: Re: 979d63d50c0c0f7bc537bf821e056cc9fe5abd38 bpf: prevent out of bounds speculation on pointer arithmetic
Date: Tue, 12 Mar 2019 04:52:34 -0700	[thread overview]
Message-ID: <20190312115234.GA29195@kroah.com> (raw)
In-Reply-To: <5d71646c-f897-2178-9d4a-fababe999f36@huawei.com>

On Mon, Mar 11, 2019 at 05:18:33PM +0800, Jason Yan wrote:
> Hi, Daniel & Greg
> 
> This patch (979d63d50c0c bpf: prevent out of bounds speculation on pointer
> arithmetic) was assigned a CVE (CVE-2019-7308) with a high score:
> 
> CVSS v3.0 Severity and Metrics:
> Base Score: 9.8 CRITICAL
> 
> And this patch is not in stable-4.4, would you please backport this patch to
> 4.4?

For a bit more context, it's also not in 4.14.y, 4.9.y, or 4.4.y.  I
found a backported series for 4.4.y in the SLES kernel tree that I could
try to import here if it really is a big deal.

I'm on the road this week, but if you could take a look at the SLES
patches and see if those work for you, and then forward them here, I
will be glad to queue them up.  Also if you could do the work for 4.14.y
and 4.9.y I'm sure lots of people would appreciate it :)

thanks,

greg k-h

  parent reply	other threads:[~2019-03-12 11:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-11  9:18 979d63d50c0c0f7bc537bf821e056cc9fe5abd38 bpf: prevent out of bounds speculation on pointer arithmetic Jason Yan
2019-03-11  9:41 ` Daniel Borkmann
2019-03-11 11:13   ` Jason Yan
2019-03-11 18:54     ` Greg KH
2019-03-12  2:01       ` Jason Yan
2019-03-12 11:52 ` Greg KH [this message]
2019-03-12 14:58   ` Jason Yan
2019-03-12 16:22     ` Greg KH
2019-03-14 14:41       ` Jason Yan
2019-03-14 14:57         ` Greg KH
2019-03-14 15:36           ` Jason Yan

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=20190312115234.GA29195@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ast@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=jannh@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=yanaijie@huawei.com \
    --cc=yi.zhang@huawei.com \
    --cc=zhaohongjiang@huawei.com \
    /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.