Intel FUBAR ... again - Kernel memory leak in nearly every Intel CPU of the last decade (Spectre hits everyone, Meltdown still Intel exclusive)

What? You didn’t buy the latest generation CPU for five years? Are you mad? How could you live without all the new features and the dramatic increase in performance because of all those added cores? And how do you think is Intel supposed to survive without all our money? If they go bankrupt it is just because of you, totally your fault!

3 Likes

games are barely playable, sometimes they’ll dip to like 120fps probably because of the 1080ti though, not the 2600k, that thing is solid.

1 Like

Oh those stupid graphics things, don’t worry about those. Just use the integrated ones from the newest i7. That should fix all your problems.

Intel believes its products are the most fastest

1 Like

i might have to make a sign and picket intel outside of the local best buy or something.

1 Like

Or…

Buy AMD :stuck_out_tongue:

j/k, people are free to buy whatever they want

Just saying that all it took for intel to be sh*t scared of amd and start taking them seriously…

Was an ‘all or nothing’ last ditch attempt from amd (who if we are honest were VERY close to circling the drain) made with the limited resources / funds that amd got from the consoles… Just imagine what they are going to do with the cash injection from ryzen / threadripper :smiley:

From here on out sh*t is going to get gud for cpu’s

It’s gpu’s I worry about now.

Amazing how things change,

pre ryzen we were worried about cpus (lack of competition / innovation etc), post ryzen now we are worried about stagnation in the gpu market :smiley:

5 Likes

Well … there’s more.

2 Likes

Interesting.

1 Like

Hi all - I’ve been out of the loop with Christmas, my Birthday, a week in Singapore (shopping for goodies!!).

I’ve heard talk about what, why, and how it will affect you. Is there any info on how to “test” systems to verify they are patched correctly?

What’s the low-down on linux so far?

DON’T MOVE!

Seen this?

Those patches cause more problems than they solve at the moment.
Wait. Just a little bit.

1 Like

Patching microcode.

Aka: How to turn an information leak vuln into a denial of service vuln. :wink:

2 Likes

Only one way to go. Intel’s next microcode update will actually set your CPU on fire, burn your house down and kill everyone in it.

But it’s fine, that means it works as intended. :+1:

1 Like

Maybe its just me, but i totally lost track at this really.
It looks like a pretty mess to me.

1 Like

When they put it like that, bit of a glaring security hole really.

with what i have seen its just a blazing dumpster fire. intel is adding fuel to there dumpster fire by the truck load. and AMD seems to be putting there fire out with a squirt gun but it is going out.

1 Like

AMD seem to be playing it close to there chest. Looking at their response. Only variant two is the near zero thing i’ve seen tossed around on the web. Everyone’s like we want zero!

But if it “aint broke dont fix it” kind of applies when they cant find a hack that would affect them. Not to say over the next year everyone and their code monkey won’t be looking for holes. Then they can address it.

5 Likes

in all honesty the hole is there its just damn hard to hit and get right. they know how to do it and they know that if others in the wild could easily do it with out knowing the secret sauce that AMD knows then they would have to address it. but as it stands they “think” they are in the clear as it would technically be a variant 2 b for it to hit them where it hurts.

In security, there is no such thing as “near zero”. You are either vulnerable or you are not. This “near zero” talk is just corporate BS from AMD and is not getting them any friends.

1 Like


I would say it has a huge impact when getting hit but it is very unlikely to get hit. So “near zero” risk in total is inaccurate, but for describing the likelyhood of an attack, it is okay.

1 Like

Sure, there are grades in Hell after all. Until there is a proper Severity Rating (CVSS etc) this “near zero” is just corporate BS from AMD.

Mark Papermaster clarified this week that they are vulnerable to Spectre, finally and end to the corporate BS.