Meanwhile, the fundamental design flaw in Intel's processor chips has led to a significant redesign effort of the Linux and Windows kernels to offset the chip-level security bug. According to the latest reports, there are some exciting details regarding the weakness and what is actually broken.
As reported on our sister site TechRadar, the fault was thought to be a major issue for users of Intel processors that are up to a decade old. Recent reports that these exploits are caused by a 'bug' or a 'flaw' and are unique to Intel products are incorrect. It argued that "many types of computing devices - with many different vendors' processors and operating systems - are susceptible to these exploits".
In the case of some discrete workloads where the performance impact will initially be higher, Intel expects the impact to be reduced by additional post-deployment identification, testing and improvement of the software updates.
Further software updates to protect machines will be issued over the next few days, Intel said.
On Tuesday the Register suggested that the flaw did not impact AMD's chips but instead primarily impacted chips from Intel. Although it's less dangerous now, it applies to a wider range of devices and could be a bit more difficult to fix. This system memory just happens to be unsecured; which means that passwords and other critical information can be stolen. Amazon and Google have also been reportedly working on security updates to their Cloud services and other products.
The flaw itself is not exactly a bug, as stated by Intel.
Barclays believes that flaws like this happen with various CPU architectures every so often, they get resolved, and historically don't create long-term issues. It said that it had already protected nearly all instances of AWS and that customers must update their own software running atop the service as well.
The good news is that if you are using Google Apps/G Suite, you don't need to take any action.