linux-kernel - spectre v2 microcodes blacklist (march update)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Sun, 4 Mar 2018 00:02:04 +0300
From:   Alexander Sergeyev <sergeev917@...il.com>
To:     David Woodhouse <dwmw@...zon.co.uk>
Cc:     Ingo Molnar <mingo@...hat.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        "H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
        Kyle Huey <me@...ehuey.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Peter Zijlstra <peterz@...radead.org>,
        linux-kernel@...r.kernel.org
Subject: spectre v2 microcodes blacklist (march update)

Hi,

the microcode revision guidance from Intel is revised once again [1] (1 Mar).

It looks like the following:

>Intel document only clears the 0xc2 microcode on *some* parts with CPUID 506E3 
>(INTEL_FAM6_SKYLAKE_DESKTOP stepping 3). For the Skylake H/S platform it's OK 
>but for Skylake E3 which has the same CPUID it isn't (yet) cleared.

is no longer a problem. CPUID 506E3 with both Skylake H/S and Skylake Xeon E3 
is labelled as "production" now.

Could we drop { INTEL_FAM6_SKYLAKE_DESKTOP, 0x03, 0xc2 } from 
spectre_bad_microcodes?

[1] 
https://newsroom.intel.com/wp-content/uploads/sites/11/2018/03/microcode-update-guidance.pdf