3 ms·
One major counterpoint: What would have happened if the AMD developer on the LKML hadn't said "AMD chips aren't affected by [one of the bugs]" before the big p
by jcranmer 9y ago
One major counterpoint:
What would have happened if the AMD developer on the LKML hadn't said "AMD chips aren't affected by [one of the bugs]" before the big public post? The big headlines would have all been about "major class of speculative execution bugs that cause data exfiltration on ARM, AMD, and Intel hardware." Only one of the bugs is Intel-specific (admittedly, the worst one), but even the Project Zero blogpost points out that it mostly focused on attacking Haswell microarchitecture.
So while Intel does have some egg on its face, ARM and AMD aren't exactly out of the woods yet. Side-channel attacks as a result of speculative execution are sort of a well-known idea, but the main big news is that they are practical to exploit and exfiltrate data. I would not be surprised to see more exploits of this type affecting different hardware vendors come out over the next year. The reason why there's so much focus on Intel is because people trying to reverse-engineer the exploit found the message saying "AMD not affected" and didn't realize that AMD is affected by some of the bugs.
Quite likely, whatever internal announcements that would have filtered up to the CEO would have focussed on the fact that other vendors are seeing some impact from these bugs (if nothing else, professional ass-covering). So it's hard to see how the CEO would actually find this information out even internally.
Edit: to put it more succinctly, Intel appears to have been preparing for an announcement of "Major class of speculative execution vulnerabilities [with particular impact to Intel]." However, the way the announcement came out was "Apparent major bug... that's Intel-specific... oh, here's the details of this bug [with related bugs affecting everybody]." That doesn't scream insider trading to me.
- theptip 9y agoFor the question of insider trading, it's irrelevant whether other companies were affected by this bug. As long as the information was not public (in this case presumably it was an embargoed secret under NDA), and that information is material (this information clearly is as Intel's stock is down about 3% today) then it's illegal to trade on that information.
- jcranmer 9y agoWell, the question is whether one would expect that Intel would be particularly affected. If the message is "everyone is boned," then there's no reason to expect Intel's share price to fall. That the message ended up being "Intel is boned" doesn't mean that insiders expected that to be the message. To clarify: it smells bad enough to be investigated... but I wouldn't vote to convict solely on the evidence presented.
- sangnoir 9y agoYou're muddying the waters. > If the message is "everyone is boned," then there's no reason to expect Intel's share price to fall That's a weak defense agains insider trading: the underlying (and incorrect) assumption is that share prices are 0-sum. It is possible - likely even - for the shares for all 3 to drop if it affects their businesses. It would still be insider trading regardless of who else on the market is affected.
- rdtsc 9y ago> What would have happened if the AMD developer on the LKML hadn't said "AMD chips aren't affected by [one of the bugs]" before the big public post? Why wouldn't they say it that way. It seems he was responding to a (justified) overreaction to mark all x86 chips vulnerable and so he pointed out explicitly that AMD wasn't. Why let his company get dragged down along with Intel unnecessary. So it is not like he jumped out on Twitter and broke "the embargo" with something like "Ha, ha, Intel is so screwed". > the big headlines would have all been about "major class of speculative execution bugs That's what Intel basically said in their PR response. But so far it seems the Intel (and maybe ARM) only bug (Meltdown) is far more serious than the Specter one. So even saying everyone is vulnerable would have been technically correct but a bit unfair toward AMD, wouldn't you say?