All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] Further information on CVE-2019-0145/CVE-2019-0146/CVE-2019-0147/CVE-2019-0148/CVE-2019-0149 for Linux?
Date: Mon, 10 Aug 2020 14:59:09 -0700	[thread overview]
Message-ID: <20200810145909.0000134f@intel.com> (raw)
In-Reply-To: <20200810184731.GA300766@eldamar.local>

On Mon, 10 Aug 2020 20:47:31 +0200
Salvatore Bonaccorso <carnil@debian.org> wrote:

> > We will get you the information, it was a mistake on our part to
> > not mention CVEs in the commit messages if/when we upstreamed the
> > patches. The only thing I can say for sure is that these have been
> > addressed in our Out-of-tree drivers, but I realize that is not
> > your question.
> 
> Thanks a lot as well for coming back to the question from Moritz, much
> appreiciated.
> 
> I noted here was a submission for i40e fixes to stable, as
> https://lore.kernel.org/stable/20200807205517.1740307-1-jesse.brandeburg at intel.com/
> . Is any of those referring to one of the above?
> 
> Thanks already for your time,

The patches to address the above issues are part of mainline kernel
5.2.0, and (upcoming) stable kernel 4.19.139, however I'm not sure if
there is anything else I need to do in order to have them backported to
4.9.y.

I hope that helps you! Thanks for bringing it to our attention.

      reply	other threads:[~2020-08-10 21:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16 20:39 [Intel-wired-lan] Further information on CVE-2019-0145/CVE-2019-0146/CVE-2019-0147/CVE-2019-0148/CVE-2019-0149 for Linux? Moritz Muehlenhoff
2020-07-28 18:10 ` Jesse Brandeburg
2020-08-02 21:04   ` Moritz =?unknown-8bit?q?M=C3=BChlenhoff?=
2020-08-10 18:47   ` Salvatore Bonaccorso
2020-08-10 21:59     ` Jesse Brandeburg [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=20200810145909.0000134f@intel.com \
    --to=jesse.brandeburg@intel.com \
    --cc=intel-wired-lan@osuosl.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.