linux-kernel - update spectre v2 microcodes blacklist

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:   Sat, 10 Feb 2018 15:31:23 +0300
From:   Alexander Sergeyev <sergeev917@...il.com>
To:     David Woodhouse <dwmw@...zon.co.uk>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>,
        "H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
        Kyle Huey <me@...ehuey.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        "Levin, Alexander (Sasha Levin)" <alexander.levin@...izon.com>,
        Peter Zijlstra <peterz@...radead.org>,
        linux-kernel@...r.kernel.org
Subject: update spectre v2 microcodes blacklist

Hello,

Intel released an updated microcode revision guidance [1] (8 Feb). The link is 
available in press-release [2], but it's quite easy to miss.

Some microcode revisions that were blacklisted before are now tested and 
pronounced production-ready:

> Lines with “***” were previously recommended to discontinue use. 
> Subsequent testing by Intel has determined that these were unaffected 
> by the stability issues and have been re-released without 
> modification.

I didn't fully match the updated revision guidance and spectre_bad_microcodes[] 
in arch/x86/kernel/cpu/intel.c, but at least microcode 0xc2 for intel skylakes 
should not be blacklisted anymore.

The update is also revelant to a recent blacklist backport to 4.9-stable:
https://patchwork.kernel.org/patch/10209021/

[1] https://newsroom.intel.com/wp-content/uploads/sites/11/2018/02/microcode-update-guidance.pdf
[2] https://newsroom.intel.com/news/security-issue-update-progress-continues-firmware-updates/