Monday, June 15th 2020
Intel Ice Lake CPUs Have a System Crashing Bug
Intel CPUs have been rather notorious for system bugs recently. Starting from 2018's Spectre and Meltdown which used speculative execution to exploit systems, the string of new vulnerabilities just continued to this day. Recently we had CrossTalk exploit which represents a threat to cloud providers, where one user could compromise another just by using the same CPU from which the virtual instances are powered. These types of exploits are even more dangerous than ones that require local access, as that is already dangerous by itself. A lot of these issues are said to be ironed out by Intel's new microarchitecture designs like Ice Lake, Tiger Lake, and future revisions.
However, it seems like Intel is encountering some problems with even the latest Ice Lake CPUs when it comes to system bugs. JetBrains, a Czech provider of software development tools has a Java programming language development environment called IntelliJ integrated development environment. It was recently reported that on MacBook Air 2020 and Microsoft Surface Pro models equipped with 10th generation Intel Ice Lake CPUs, IntelliJ IDE causes system restart or a complete OS crash. In the report, the CPU ran in a Linux VM that isolates itself from MacOS so the macOS XNU kernel is not to blame. In the report thread, another user running Windows on Microsoft Surface Pro experienced the crash as well.Thanks to community testing, we have found out that these issues are not just a software bug, however, it is a rather CPU specific bug that only occurs on Intel Ice Lake processors. Intel recently updated the CPU microcode and there is no improvement. It seems like the IntelliJ IDE has a specific sequence of instructions that trigger Ice Lake CPUs to crash OS. This behavior is concerning as this could be used for a possible exploit. Again, cloud providers are at risk here as if you crash the system the whole instance could crash. Of course server Ice Lake parts are yet to arrive, but the bug could be hidden in the core of the CPU design. Even with the latest microcode update Ice Lake CPUs are still crashing with this software, so we have to see how Intel responds to this.
Source:
JetBrains YouTrack
However, it seems like Intel is encountering some problems with even the latest Ice Lake CPUs when it comes to system bugs. JetBrains, a Czech provider of software development tools has a Java programming language development environment called IntelliJ integrated development environment. It was recently reported that on MacBook Air 2020 and Microsoft Surface Pro models equipped with 10th generation Intel Ice Lake CPUs, IntelliJ IDE causes system restart or a complete OS crash. In the report, the CPU ran in a Linux VM that isolates itself from MacOS so the macOS XNU kernel is not to blame. In the report thread, another user running Windows on Microsoft Surface Pro experienced the crash as well.Thanks to community testing, we have found out that these issues are not just a software bug, however, it is a rather CPU specific bug that only occurs on Intel Ice Lake processors. Intel recently updated the CPU microcode and there is no improvement. It seems like the IntelliJ IDE has a specific sequence of instructions that trigger Ice Lake CPUs to crash OS. This behavior is concerning as this could be used for a possible exploit. Again, cloud providers are at risk here as if you crash the system the whole instance could crash. Of course server Ice Lake parts are yet to arrive, but the bug could be hidden in the core of the CPU design. Even with the latest microcode update Ice Lake CPUs are still crashing with this software, so we have to see how Intel responds to this.
26 Comments on Intel Ice Lake CPUs Have a System Crashing Bug
Intel is going to have to issue a hardware recall if they can't patch this in microcode. Even if they can, it's almost certainly going to cause significant slowdown a la Bulldozer TLB. I smell a class action lawsuit...
Same goes for reviewers like some had massive problems before, on and a good a mount of time after release date of the Navi cards and others had no issues at all.
Even some users with the same hardware setup can doesn't need to have the same issues and this is what causes the headache for AMD.
I know that AMD takes every NAVI issue reported seriously but if they as said before cannot replicate it in their test environment they cannot fix them as easy you change a setting your card crashes AMD changes the same setting and the card crashes then it's easier then they cannot get the same settings to crash.
It's not like every motherboard vendor send AMD a copy of every board that's made to test with.
LLT made a video recently and there is at least one Ice lake bug related to after fx.
This article, if you took the time to read it and understand it, explains a totally different scenario where using a Java tool will in some specific case give you a crash.
The second paragraph I cited an example about another known ice lake bug, probably not related to the bug reported by the article but affects many users.
When you have to rush product asap on the market to avoid loosing too much, you can end up with issues.