Linked by Thom Holwerda on Mon 29th Jan 2018 23:17 UTC
Windows

Microsoft has released an update that disables Intel's microcode Spectre mitigations.

Intel has reported issues with recently released microcode meant to address Spectre variant 2 (CVE 2017-5715 Branch Target Injection) - specifically Intel noted that this microcode can cause "higher than expected reboots and other unpredictable system behavior" and then noted that situations like this may result in "data loss or corruption". Our own experience is that system instability can in some circumstances cause data loss or corruption. On January 22, Intel recommended that customers stop deploying the current microcode version on affected processors while they perform additional testing on the updated solution. We understand that Intel is continuing to investigate the potential effect of the current microcode version, and we encourage customers to review their guidance on an ongoing basis to inform their decisions.

This whole thing is a mess.

Permalink for comment 653366
To read all comments associated with this story, please click here.
RE[2]: No solution
by aaronb on Wed 31st Jan 2018 13:44 UTC in reply to "RE: No solution"
aaronb
Member since:
2005-07-06

The separation of user space and kernel space has been a specified feature (Privilege levels) since the Intel 386 (possibly earlier) on the x86 architecture. Meltdown blurs the line between the two as speculative execution seems to be able to speculate with kernel space data from user mode processes and allows the speculated kernel space data to be leaked to user space. If the leaking did not occur the feature would be working as designed.

In my opinion this is a bug that requires software mitigation for current Intel CPUs and hopefully the next generation of Intel CPUs will not be susceptible to Meltdown.

This issue seems to have taken the tech community by surprise, needs to be addressed as quickly as possible due to the severity and is challenging to fix.

Reply Parent Score: 3