It was so bad that the chip maker has to be elated to have CES, the massive customer technology show going on this week in Las Vegas, as a way to change the subject and target on the other work they are doing.
For starters, CEO Brian Krzanich had to deal with the elephant in the room at the company keynote on Monday. Spectre and Meltdown patches were appearing to 90 % of the company’s affected chips by next week. That was good news for a company under annoy for what my friend Ingrid Lunden described without exaggeration as “…perhaps its largest security scare in its history.”
It didn’t help matters when Intel’s patch proven buggy and caused some systems to reboot.
In case you don’t know what that trouble was about, it started last week when The Register, a U.K. tech publication, published an article blowing the lid off an Intel kernel security problem in their CPU chips. This is not a little matter.
It has the potential to permit hackers unimpeded access to the chip’s kernel where information like your passwords and encryption keys are stored in a probably secure area of the chip architecture.
It later turned out there were actually two chip vulnerability issues, one that had an impact on just Intel chips called Meltdown and one called Spectre that affected Intel and other chips, including AMD and ARM processors and even IBM’s Power chips. We also learned that another Intel rival, Nvidia, also declared several of its chips have been affected. (If you were running a Raspberry Pi computer, you were spared.)
Mitigation efforts have been appearing fast and furious from every corner: from chip vendors, from the OS vendors like Microsoft and Apple and from very nearly anyone else. There is concern that the mitigation solutions could in fact slow down computers substantially. While it’s still not broadly known just how much that will affect personal computers and servers, Microsoft published a blog post this week outlining their benchmarks displaying different degrees of performance degradation after achieving the Spectre and Meltdown mitigation solutions on machines running Windows. So did Intel, which found some performance hits and Google, which claimed it didn’t have any.
While this wasn’t just an Intel issue, it is, as Lunden pointed out, “one of the world’s largest chip makers,” and as such it bore the brunt of the bad reaction. It didn’t help that the company had been aware of the susceptibility for some time or that Krzanich had sold a substantial amount of stock in November, and had filed the intent to sell those shares after the company had learned about the bugs.
This week at CES, the company addressed the issue (at least to some extent), as Lunden reported, but a show like CES has the benefit of being a stage for a number of new technologies. The company started making a flurry of announcements, planned long before the chip flaws became public last week.
It began with the announcement of a 49 Qubit quantum computing chip. If you want to change the conversation, building one of the fastest quantum computing chips in the world is one way to do it (IBM announced in November that it had built a 50 qubit prototype).
In fact, the company made a total of six announcements that we covered at TechCrunch this week involving drones, autonomous cars and cinematic VR, among other things.
All of this seems to me to be about utilizing various degrees of showmanship and technological acumen to try to change the subject. It’s likely that Meltdown and Spectre will continue to haunt Intel and other chip makers for some time to appear.
While it’s essential to note that there haven’t been any documented breaches from this vulnerability, it has created a serious perception issue for Intel and its competitors, especially since they have chosen from an engineering perspective to optimize their chips for speed over security for many years, paving the way for these vulnerabilities.