Fact is they are still patching away! And yes I have seen no public disclosure on many of the problems. Try asking Intel for help, it is a brick wall. My guess

Fact is they are still patching away! And yes I have seen no public disclosure on many of the problems. Try asking Intel for help, it is a brick wall. My guess is that they made a huge mistake, that they thought that high precision timers were needed, and they did not put the effort into otherwise fixing the problems. Lack of sharing probably made it much worse. They had still not addressed these at the public disclosure date. They either realized the mistake themselves or various people told them of their mistakes, and they were left with known vulnerable products on the market that they had no hope of fixing in a timely manner. At that point they could have advised their users to move to alternative products, e.g. Google had a head start, but that would likely have ended them, most people would not come back many months later when they claim to have fixed the problems, and that is a big expense for them! Another alternative was to take drastic coding measures, lfence branch paths, but at a high performance loss, they did not do that either, again who wants a slow product if the competition has not also taken the same action. The really kicker is people had been trying to get them to move on this for years and they had been resisting it strongly.