News for hackers. Stuff that matters.
Re:Meltdown and Spectre Linux kernel status by Santosh83 on Saturday January 06, 2018 @12:15PM (#16086204)
What I'd like to know is how effective are these OS updates (both Linux and Windows) without the associated firmware updates through microcode or BIOS/UEFI flashing. My system is a few years old and I don't expect the OEM to release BIOS/UEFI updates for this model.

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.

Re:Meltdown and Spectre Linux kernel status by JdeBP on Saturday January 06, 2018 @12:58PM (#16086519)
The microcode updates that people have been mentioning are not updates to your motherboard's firmware, EFI or otherwise. They are updates to the code that runs inside your central processor chip, the so-called microcode, that does the work of understanding and enacting processor instructions (in all programs, from the programs in your firmware to the programs that you download and run from the WWW).

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)

Re:Meltdown and Spectre Linux kernel status by davidjade on Saturday January 06, 2018 @01:41PM (#16086743)
Windows, at least for right now, does not seem to be updating CPU microcode during boot. If you run the PowerShell Get-SpeculationControl script that gives you the status of the updates it states that the CVE-2017-5715 fix requires hardware support. If you don't have it you are told to get a BIOS update from your OEM. WIthout it, the status for CVE-2017-5715 is listed as not enabled due to missing hardware support.

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.

Re:Meltdown and Spectre Linux kernel status by newman314 on Saturday January 06, 2018 @02:50PM (#16087068)
This appears to be my experience too. I'm checking a few VMs and they are showing as missing hw support.

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.

Re:Meltdown and Spectre Linux kernel status by cyann on Monday January 08, 2018 @02:31PM (#16099456)
MinVmVersionForCpuBasedMitigations is for VM/Hyper-V: https://docs.microsoft.com/en-us/virtualization/hyper-v-on-w...
Re:Meltdown and Spectre Linux kernel status by JdeBP on Saturday January 06, 2018 @01:48PM (#16086785)
The situation with Windows NT is slightly tricky, and underreported. I have pointed to this once already on this page, but it bears repeating.

* https://news.ycombinator.com/item?id=16076660

Re:Meltdown and Spectre Linux kernel status by tmitchell on Saturday January 06, 2018 @06:40PM (#16088134)
VMware distributes a driver[1] one can install to patch the microcode on Windows at runtime. If these updates need to be recognized before OS boot, this may not mitigate the dangers. But in my test lab, HWiNFO64 shows the current microcode version.

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...

Re:Meltdown and Spectre Linux kernel status by wilun on Saturday January 06, 2018 @02:38PM (#16087023)
The microcode updates can typically be stored and loaded by the motherboard fw, though, and some OSes don't even load their own version.
Re:Meltdown and Spectre Linux kernel status by _wmd on Saturday January 06, 2018 @01:33PM (#16086706)
AFAIK on Intel it's not possible to load a microcode update over the top of one already loaded by your firmware, so if the firmware shipped an older update, the firmware really needs to be updated. (Please someone correct me if this isn't the case -- I can't even remember where I read this)
Re:Meltdown and Spectre Linux kernel status by amluto on Saturday January 06, 2018 @05:25PM (#16087814)
Nope, the OS or hypervisor (but not a guest) can freely update whenever they like, as long as all the updates are to newer versions. For updates that modify visible CPU features, like these, it's helpful to apply them before boot. Linux has a mechanism to apply "early" updates from initramfs that effectively function before the kernel boots. I don't think other OSes can do that.
Re:Meltdown and Spectre Linux kernel status by wilun on Saturday January 06, 2018 @02:36PM (#16087015)
I don't think this is correct at all. I've personally seen the contrary happening.

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.

Re:Meltdown and Spectre Linux kernel status by frik on Saturday January 06, 2018 @01:10PM (#16086587)
As I understand the microcode updates get installed by Linux distros and Windows by updates. Microcodes are loaded by the CPU at every boot.

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.

Re:Meltdown and Spectre Linux kernel status by bhauer on Saturday January 06, 2018 @12:34PM (#16086360)
I share your concern. Based on my admittedly loose understanding, although the Spectre vulnerability is "more difficult" to exploit, I suspect it's a matter of time before exploits become more common. And the Spectre vulnerability is the one that requires a BIOS/firmware update.

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.

Re:Meltdown and Spectre Linux kernel status by danieldk on Saturday January 06, 2018 @02:14PM (#16086923)
Microcode updates can be applied on boot through the BIOS/EFI firmware, but also by the operating system. Linux (I don't know about Windows) has facilities to update the microcode on boot:

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.

Re:Meltdown and Spectre Linux kernel status by cthalupa on Saturday January 06, 2018 @12:43PM (#16086425)
>And the Spectre vulnerability is the one that requires a BIOS/firmware update.

One of the Spectre variants. The other isn't mitigated by it and will require an lfence on your sensitive areas of apps.

Re:Meltdown and Spectre Linux kernel status by moe on Saturday January 06, 2018 @06:43PM (#16088149)
This is a key detail that gets glossed over too much for my liking.

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...

Re:Meltdown and Spectre Linux kernel status by rhizome on Saturday January 06, 2018 @12:50PM (#16086472)
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

Buy stock in Gigabyte, MSI, etc.

Re:Meltdown and Spectre Linux kernel status by mjevans on Saturday January 06, 2018 @02:03PM (#16086869)
If you're running a Windows machine, I've no idea how it handles the microcode updates.

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.

Re:Meltdown and Spectre Linux kernel status by pqh on Wednesday January 10, 2018 @11:14AM (#16116062)
I downloaded the microcode updates from Intel, but hesitate to apply them because one of the expected directories does not exist on Manjaro, so I'm out of my element on how supported the update would be. Do you happen to know if in general microcode updates are distributed in packages? It seems that's probably the case, and if so, I'm fine waiting.
Re:Meltdown and Spectre Linux kernel status by chomp on Saturday January 06, 2018 @12:38PM (#16086387)
Only kinda effective. Retpoline on Skylake and later isn't completely reliable as a mitigation for one of the spectre variants, and IBRS is one of the processor features that will supposedly correct that.

You'll still be vulnerable, it'll just add another layer of difficulty to the exploit.