>It has the potential to allow hackers unimpeded access to the **chip’s kernel** where information like your passwords and encryption keys are **stored in a supposedly secure area of the chip architecture**.
While the rest of the article was seemingly on point, these two little errors stand out to me:
* It's not the processor's kernel. It's the operating system's kernel.
* The kernel is stored in RAM, for the most part. Tiny pieces of it can move to the cache temporarily, but to say that the whole operating system kernel is stored in the CPU cache is a bit incorrect. What they're trying to convey is that operations on kernel memory have hardware-enforced permissions, namely CPU modes. Only code executing in the context of ring 0 can execute certain CPU instructions or access certain memory locations such as kernel memory locations.
You'd think a technology publication would understand the basics.
They already did a pretty good job of diverting the conversion by pushing the media to include both a bug that affects themselves and one that affects those of their rivals -- although only one has any serious performance impact issues -- the one that impacts their silicon and not others'. That was some sly and dishonest maneuvering, which, I feel, really exposes the dark underbelly of their relationship and influence over a lot of mainstream media.
Is there a definitive list that says that exactly which models of Intel and AMD processors are affected ?
Wow what a shitty article.
The author is basically implying that because Intel didn't lead every one of their presentations or booth spiels with "Hey Meltdown is serious business and we're very sorry" that they're trying to "change the subject".
Man, it's CES, the subject is about new technologies, so that's what they did.
I was considering upgrading my cpu, now it feels like I'm buying a broken product, any ideas when improved cpu's will hit the market?
Huh? BK spent his entire intro discussing intel's response to the issues