All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: linux-integrity@vger.kernel.org
Cc: Kari Hiitola <kari@varaani.com>,
	linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org
Subject: Fixing CVE-2017-15361
Date: Wed, 25 Oct 2017 15:44:38 +0200	[thread overview]
Message-ID: <20171025134438.vgh6tzkups2tujps@linux.intel.com> (raw)

I'm implementing a fix for CVE-2017-15361 that simply blacklists
vulnerable FW versions. I think this is the only responsible action from
my side that I can do.

/arkko

WARNING: multiple messages have this Message-ID (diff)
From: jarkko.sakkinen@linux.intel.com (Jarkko Sakkinen)
To: linux-security-module@vger.kernel.org
Subject: Fixing CVE-2017-15361
Date: Wed, 25 Oct 2017 15:44:38 +0200	[thread overview]
Message-ID: <20171025134438.vgh6tzkups2tujps@linux.intel.com> (raw)

I'm implementing a fix for CVE-2017-15361 that simply blacklists
vulnerable FW versions. I think this is the only responsible action from
my side that I can do.

/arkko
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2017-10-25 13:44 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-25 13:44 Jarkko Sakkinen [this message]
2017-10-25 13:44 ` Fixing CVE-2017-15361 Jarkko Sakkinen
2017-10-25 14:17 ` Matthew Garrett
2017-10-25 14:17   ` Matthew Garrett
2017-10-25 18:53   ` Jarkko Sakkinen
2017-10-25 18:53     ` Jarkko Sakkinen
2017-10-25 20:22     ` Jerry Snitselaar
2017-10-25 20:22       ` Jerry Snitselaar
2017-10-26 11:01       ` Jarkko Sakkinen
2017-10-26 11:01         ` Jarkko Sakkinen
2017-10-25 22:26     ` Peter Huewe
2017-10-25 22:26       ` Peter Huewe
2017-10-26 11:16       ` Jarkko Sakkinen
2017-10-26 11:16         ` Jarkko Sakkinen
2017-10-26 11:27         ` Jarkko Sakkinen
2017-10-26 11:27           ` Jarkko Sakkinen
2017-10-26 12:59         ` Michal Suchánek
2017-10-26 12:59           ` Michal Suchánek
2017-10-26 14:06           ` Jarkko Sakkinen
2017-10-26 14:06             ` Jarkko Sakkinen
2017-10-26 14:06             ` Jarkko Sakkinen
2017-10-26 14:57             ` Michal Suchánek
2017-10-26 14:57               ` Michal Suchánek
2017-10-26 14:57               ` Michal Suchánek
2017-10-26 17:02               ` Jarkko Sakkinen
2017-10-26 17:02                 ` Jarkko Sakkinen
2017-10-26 17:02                 ` Jarkko Sakkinen
2017-10-26 17:03                 ` Jarkko Sakkinen
2017-10-26 17:03                   ` Jarkko Sakkinen
2017-10-26 17:03                   ` Jarkko Sakkinen
2017-10-26 15:46         ` Alexander.Steffen
2017-10-26 15:46           ` Alexander.Steffen at infineon.com
2017-10-26 17:08           ` Jarkko Sakkinen
2017-10-26 17:08             ` Jarkko Sakkinen
2017-10-26 15:42     ` Alexander.Steffen
2017-10-26 15:42       ` Alexander.Steffen at infineon.com
2017-10-26 17:00       ` Jarkko Sakkinen
2017-10-26 17:00         ` Jarkko Sakkinen
2017-10-26 15:51     ` Alexander.Steffen
2017-10-26 15:51       ` Alexander.Steffen at infineon.com
2017-10-26 19:07       ` Jarkko Sakkinen
2017-10-26 19:07         ` Jarkko Sakkinen

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=20171025134438.vgh6tzkups2tujps@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=kari@varaani.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@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 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.