The Vrije Universiteit Amsterdam researchers who alerted Intel to the problems have told the New York Times that Intel apparently ignored key proof-of-concept exploits when developing the May update, and should have found the relevant flaws even without those ready-made examples. The team refused to stay quiet with the November patch knowing that there were still issues. There are also criticisms of Intel's overall approach -- instead of tackling the underlying problem, it's allegedly focused more on patching variants of that problem as they pop up.

The initial problem affected many processors released since 2011 and applied regardless of your operating system. Software-level patches have mitigated some of the security problems on top of Intel's microcode solutions.

We've asked Intel for comment. This isn't a great look for the chip giant, whatever its response. As the researchers warned, the usual secrecy that governs vulnerability disclosures could hurt users here. Hackers could take advantage of security holes that people don't realize are still open, and the flaw itself wasn't all that secret -- it leaked to the point where the researchers were told about their own discovery. There may be substantial work ahead (including possible chip design changes) before Intel's CPUs are more trustworthy.

Update 11/13 3:05PM ET: Intel tells Engadget that it has been "very public" about its approach to disclosures, and takes "seriously" all vulnerabilities no matter who discovers them. You can read the full statement below. The company also pointed to Twitter comments from Daniel Gruss, who played a role in the disclosure. Gruss said Intel took concerns "very seriously" and has improved its approach "substantially" over the past year. Those are fair points, but it remains true that Intel didn't patch all the known issues in one go and still had communication issues.