| 1 | |
| 2 |
|
| 3 | =============
|
| 4 | Old Microcode
|
| 5 | =============
|
| 6 |
|
| 7 | The kernel keeps a table of released microcode. Systems that had
|
| 8 | microcode older than this at boot will say "Vulnerable". This means
|
| 9 | that the system was vulnerable to some known CPU issue. It could be
|
| 10 | security or functional, the kernel does not know or care.
|
| 11 |
|
| 12 | You should update the CPU microcode to mitigate any exposure. This is
|
| 13 | usually accomplished by updating the files in
|
| 14 | /lib/firmware/intel-ucode/ via normal distribution updates. Intel also
|
| 15 | distributes these files in a github repo:
|
| 16 |
|
| 17 | https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files.git
|
| 18 |
|
| 19 | Just like all the other hardware vulnerabilities, exposure is
|
| 20 | determined at boot. Runtime microcode updates do not change the status
|
| 21 | of this vulnerability.
|