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.

Permalink for comment 653364
To read all comments associated with this story, please click here.
RE[3]: No solution
by Megol on Wed 31st Jan 2018 11:17 UTC in reply to "RE[2]: No solution"
Member since:

"IMO the Meltdown thing is a bug (not all think so).

This isn't. The processor does what it was designed to do, what it is documented to do in a way that is documented. No bug.

Not sure if you're trolling or not.

Obviously not trolling. But I know what I'm talking about.

Access to high privileged kernel-mode memory from unprivileged usermode process is not documented and it is definitely _not_ a designed behaviour.

But Spectre doesn't allow that _in_the_way_the_processor_is_defined_.

Please, show me the description of this "feature" in architecture reference manual.

That kernel mode programs can read memory read kernel memory? Download and read:

Drill down into the description of how memory protection works.

Reply Parent Score: 3