[CentOS] /lib/firmware/microcode.dat update on CentOS 6

Thu Jan 25 00:41:26 UTC 2018
Leon Fauster <leonfauster at googlemail.com>

> Am 24.01.2018 um 22:22 schrieb Chris Adams <linux at cmadams.net>:
> Once upon a time, Chris Murphy <lists at colorremedies.com> said:
>> "We recommend that OEMs, cloud service providers, system
>> manufacturers, software vendors and end users stop deployment of
>> current versions."  Current versions of what? Microcode?
> Well, that's the only thing Intel provides for CPUs, so that's all it
> can be.
>> What these means for people who have CPUs which were not crashing
>> (rebooting being a new euphemism for crashing) , but saw variant 2
>> Spectre mitigation with the 20180108 microcode, will lose full
>> mitigation until Intel gets its ducks into a row.
> Lots of people weren't seeing issues, but that's in part because Intel's
> updated microcode release only actually updated microcode for recent
> CPUs.  I have many servers that aren't crashing, but that's because
> Intel hasn't actually even tried to fix the microcode for their CPUs
> yet.

Comparing microcode-20171117 with microcode-20180108 shows that 
from the 94 ucode files only 19 where updated

$ diff -r --brief microcode-20171117 microcode-20180108
Files microcode-20171117/intel-ucode/06-3c-03 and microcode-20180108/intel-ucode/06-3c-03 differ
Files microcode-20171117/intel-ucode/06-3d-04 and microcode-20180108/intel-ucode/06-3d-04 differ
Files microcode-20171117/intel-ucode/06-3e-04 and microcode-20180108/intel-ucode/06-3e-04 differ
Files microcode-20171117/intel-ucode/06-3f-02 and microcode-20180108/intel-ucode/06-3f-02 differ
Files microcode-20171117/intel-ucode/06-3f-04 and microcode-20180108/intel-ucode/06-3f-04 differ
Files microcode-20171117/intel-ucode/06-45-01 and microcode-20180108/intel-ucode/06-45-01 differ
Files microcode-20171117/intel-ucode/06-46-01 and microcode-20180108/intel-ucode/06-46-01 differ
Files microcode-20171117/intel-ucode/06-47-01 and microcode-20180108/intel-ucode/06-47-01 differ
Files microcode-20171117/intel-ucode/06-4e-03 and microcode-20180108/intel-ucode/06-4e-03 differ
Files microcode-20171117/intel-ucode/06-55-04 and microcode-20180108/intel-ucode/06-55-04 differ
Files microcode-20171117/intel-ucode/06-56-02 and microcode-20180108/intel-ucode/06-56-02 differ
Files microcode-20171117/intel-ucode/06-56-03 and microcode-20180108/intel-ucode/06-56-03 differ
Files microcode-20171117/intel-ucode/06-5e-03 and microcode-20180108/intel-ucode/06-5e-03 differ
Files microcode-20171117/intel-ucode/06-7a-01 and microcode-20180108/intel-ucode/06-7a-01 differ
Files microcode-20171117/intel-ucode/06-8e-09 and microcode-20180108/intel-ucode/06-8e-09 differ
Files microcode-20171117/intel-ucode/06-8e-0a and microcode-20180108/intel-ucode/06-8e-0a differ
Files microcode-20171117/intel-ucode/06-9e-09 and microcode-20180108/intel-ucode/06-9e-09 differ
Files microcode-20171117/intel-ucode/06-9e-0a and microcode-20180108/intel-ucode/06-9e-0a differ
Files microcode-20171117/intel-ucode/06-9e-0b and microcode-20180108/intel-ucode/06-9e-0b differ
Files microcode-20171117/microcode.dat and microcode-20180108/microcode.dat differ
Files microcode-20171117/releasenote and microcode-20180108/releasenote differ

Microcode ID?

$ awk '/cpu family/||/model\t/||/stepping/' /proc/cpuinfo |sort |uniq 

and convert it into hex