Not really a new issue, just added dimension to the existing one.
From my reading, I understand that Intel is saying there's an Intel microcode fix and an Intel SDK. Already available or underway. But securing this vulnerability properly means that non-Intel devs have to actually revise their softwares with this SDK stuff - something Intel can support, assist, even direct, but not something Intel can actually do for non-Intel products. Windows is obviously the Big Deal here, Intel can't make Windows secure, they can only provide Microsoft with the tools and resources that Microsoft needs to make Windows secure. Though of course other operating systems/hypervisors/etc need to be updated by their own non-Intel devs as well.
"All opinions are not equal. Some are a very great deal more robust, sophisticated and well supported in logic and argument than others." - Douglas Adams
[/Korth]
