The reboot problem affecting Spectre/Meltdown-patched systems is more widespread than initially thought, Intel announced Wednesday.
Last week, Intel revealed that "a few customers" have experienced higher-than-usual system reboots after applying the firmware updates. At that time, Navin Shenoy, Intel's Data Center Group EVP and General Manager, said the problem hit firmware updated systems running Intel's older Broadwell and Haswell CPUs. Now we know the problem affects newer chips as well.
"We have determined that similar behavior occurs on other products in some configurations, including Ivy Bridge-, Sandy Bridge-, Skylake-, and Kaby Lake-based platforms," Navin wrote in a Wednesday blog post. "We have reproduced these issues internally and are making progress toward identifying the root cause."
- How to Protect Your Devices Against Meltdown, Spectre Bugs How to Protect Your Devices Against Meltdown, Spectre Bugs
As it works to find the root cause of this reboot problem, Intel plans to "start making beta microcode updates available to OEMs, cloud service providers, system manufacturers, and software vendors next week for internal evaluation purposes," the company wrote.
Real Life. Real News. Real Voices
Help us tell more of the stories that matterBecome a founding member
Despite the reboot problem, Intel says all current updates offer protection against Spectre Variant 2. Meanwhile, "Variants 1 (Spectre) and Variant 3 (Meltdown) continue to be mitigated through system software changes from operating system and virtual machine vendors," Intel wrote. For more information, see this Intel Security Center page.
At this point, Intel has issued firmware updates for 90 percent of CPUs it has introduced in the past five years. The Meltdown and Spectre flaws relate to how a CPU handles tasks that it thinks a PC will need to perform in the future, known as speculative execution. According to Google's Project Zero security team, in a worst case scenario the flaws could be exploited to reap sensitive information from these commands-in-waiting.
Subscribe to the newsletter news
We hate SPAM and promise to keep your email address safe