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

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.

Thread beginning with comment 653423
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: No solution
by viton on Fri 2nd Feb 2018 03:42 UTC in reply to "RE[3]: No solution"
Member since:

My option is also that Meltdown is a bug

But wasn't it you was you who said No bug? ;)

It isn't documented, the official documentation doesn't mention this but say that illegal accesses will cause a protection exception.

You need memory protection to _prevent unauthorized access_, not to fire-up some exceptions.

Meltdown could be implemented without Spectre-style attack, but with the help of TSX extensions.

Reply Parent Score: 2