More Intel speculative execution vulnerabilities
mdsattacks.com
More Intel speculative execution vulnerabilities
1–10 of 262 posts
Re: More Intel speculative execution vulnerabilities
#2[deleted]
Re: More Intel speculative execution vulnerabilities
#3another 0-4% performance hit for skylake
Re: More Intel speculative execution vulnerabilities
#4Another nail in the casket lake. Is the solution just to throw everything out and start again? Do we just abandon speculative execution?
Re: More Intel speculative execution vulnerabilities
#5another 0-4% performance hit for skylake
The really damning part is that it applies even for processors that are supposedly fixed in silicon because Intel dropped the ball by playing wack-a-mole with proof of concept exploits instead of thoroughly building their chips with security in mind.
If the history of Microsoft and Windows security is any indication, it'll take Intel many many years to turn that ship around.
There's a question of whether AMD has been mostly unaffected only because their chips haven't received as much scrutiny, but for the time being it does seem that if you care about security, you'd better go with Epyc.
Re: More Intel speculative execution vulnerabilities
#6So Intel failed to mitigate the vulnerability when it was first reported. Then they extended the embargo from May until November.
And they still didn't fix it.
What's going on with Intel? Like they're going all in with lying in benchmarks against AMD and straight up forgetting what has been reported as security issues.
Re: More Intel speculative execution vulnerabilities
#7AMD is suffering much less from these flaws. Seems they didn't ignore as many security boundaries with their implementation.
Re: More Intel speculative execution vulnerabilities
#8AMD is suffering much less from these flaws. Seems they didn't ignore as many security boundaries with their implementation.
or there are just as many vulnerabilities on amd but researched less
Re: More Intel speculative execution vulnerabilities
#9AMD is suffering much less from these flaws. Seems they didn't ignore as many security boundaries with their implementation.
AMD (and ARM OoO chips) are vulnerable to Spectre variant 1 (bypass in-process array bounds checking) but not to the vast majority (any?) of the other issues which are Intel-only.
AMD chips don't have the feature that speculation failure is determined at instruction commit time when it is already too late, so most issues just can't happen.
Re: More Intel speculative execution vulnerabilities
#10Running the below over my machines gives me back the 8-30% cycles I originally paid for, depending on load type. This will
have to do until everything is swapped to AMD. Note you only need 'mitigations=off' in later kernels.
- name: Disable CPU-sapping security mitigations
become: yes
lineinfile:
path: /etc/default/grub
line: GRUB_CMDLINE_LINUX_DEFAULT="noresume noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off mitigations=off"
- name: Update grub
become: yes
command: /usr/sbin/grub-mkconfig -o /boot/grub/grub.cfg