Firmware updates are largely irrelevant to this issue, only being involved in the sense that one way to perform microcode updates is for your machine's firmware to upload the new microcode image file. But that is just one way for that to be done; your operating system can do it, too.
* http://inertiawar.com/microcode/
* https://news.ycombinator.com/item?id=16081366
* https://newsroom.intel.com/wp-content/uploads/sites/11/2018/... (https://news.ycombinator.com/item?id=16079910)
Of all of my computers only one has been issued a BIOS update so far. I ran the PowerShell script before and after installing the BIOS. Installing the BIOS flipped the status of the fix for CVE-2017-5715 to on.
I also ran the free HwInfo utility that will show the microcode revision before and after installing the Windows update and before and after installing the BIOS. It only ever changed with the BIOS update.
I hope this changes and Windows does start updating CPU microcode. I also have a few older motherboard's that aren't likely to ever see a BIOS update again.
Do note that Microsoft appears to have updated their doc in the last day or so. They are now saying that three registry settings need to be set (instead of 2 previously).
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management" /v FeatureSettingsOverride /t REG_DWORD /d 0 /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management" /v FeatureSettingsOverrideMask /t REG_DWORD /d 3 /f
reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization" /v MinVmVersionForCpuBasedMitigations /t REG_SZ /d "1.0" /f
Some quick Googling seems to indicate that Windows has the ability to update microcode.http://forum.notebookreview.com/threads/how-to-update-microc...
Maybe this will happen with a later update from Microsoft as I'm doubtful that BIOS updates will happen with at least one of my systems.
The Intel[2] and AMD[3] microcode can be downloaded but I can't vouch for how many Meltdown/Spectre mitigations these versions contain. The Intel one is dated 2017-11-17.
[1] https://labs.vmware.com/flings/vmware-cpu-microcode-update-d...
[2] https://downloadcenter.intel.com/download/27337/Linux-Proces...
[3] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/lin...
EDIT: however for some rare features, it is preferable to have them loaded by the firmware. I don't know if this is the case here.
The question is, how can one check if the CPU already got the microcode update?
Can a OS running inside a VM (over Intel VT ring-1) patch the CPU's microcode? (e.g. Linux host, and Win guest patches CPU's microcode) Nothing seems impossible anymore.
So that's a bit alarming for me since at least one of my several workstations is using a 5+ year old desktop board (an Intel board, ironically) that has been end-of-lifed according to its BIOS downloads support page. Meanwhile, some of the bigger server motherboard vendors (e.g., SuperMicro) are not yet prepared to supply firmware updates for recent motherboards.
Recognizing that the operating system vendors/maintainers are not responsible for our systems' BIOS and hardware, the flippant advice to "talk with your device's vendor" gives me a sinking feeling. (E.g., Microsoft: "Consult with the device manufacturer about the firmware version that has the appropriate update for your CPU.") As a technical person, I am going to find it difficult to bring all of my hardware—especially the older hardware—up to snuff for coping with these vulnerabilities. I fear for people who are less technically inclined.
https://wiki.archlinux.org/index.php/microcode
https://wiki.debian.org/Microcode
Also, directly from Intel:
While the regular approach to getting this microcode update is via a BIOS update, Intel realizes that this can be an administrative hassle. The Linux operating system has a mechanism to update the microcode after booting. For example, this file will be used by the operating system mechanism if the file is placed in the /etc/firmware directory of the Linux system.
Source: https://downloadcenter.intel.com/download/27337/Linux-Proces...
Apple probably delivers them through EFI updates, but of course, getting updated EFI firmware from Apple was never a problem.
One of the Spectre variants. The other isn't mitigated by it and will require an lfence on your sensitive areas of apps.
No OS or Firmware update will fully fix Spectre.
All applications that interpret untrusted code (such as Web browsers) also have to be patched.
https://gist.github.com/woachk/2f86755260f2fee1baf71c90cd653...
Buy stock in Gigabyte, MSI, etc.
For LINUX (and probably BSD/etc users):
https://wiki.archlinux.org/index.php/microcode#Enabling_Inte...
Your distribution probably has a firmware package that has this bootloader stub. It applies the latest microcode updates just before your OS actually begins starting up (but for Linux after the Kernel has initialized things and is preparing to hand off to the initrd).
Yes, this is something that needs to happen at every boot; they don't get burned in to the CPU.
You'll still be vulnerable, it'll just add another layer of difficulty to the exploit.
Will the OS/microcode update still at least partially protect me or will I have to be super-paranoid about apps and javascript for the remainder of this machine's life?
BTW, my machine is just a normal desktop/laptop, so no server stuff running or expected.