Fixed in January. https://blogs.intel.com/technology/2020/06/ipas-security-advisories-for-june-2020/ https://blogs.intel.com/technology/2020/06/ipas-security-a

Fixed in January. https://blogs.intel.com/technology/2020/06/ipas-security-advisories-for-june-2020/ https://blogs.intel.com/technology/2020/06/ipas-security-adv... > Finally, in January 2020 we released INTEL-SA-00329 addressing two side-channel issues. Specifically, CVE-2020-0549 addressing an issue called “L1D Eviction Sampling” which has been referred to by researchers as “CacheOut”. The CacheOut researchers recently informed us of a new paper referred to as SGAxe. It is important to note that SGAxe relies on CVE-2020-0549 which has been mitigated in microcode (confirmed by the researchers in their updated CacheOut paper) and distributed out to the ecosystem. And from the CacheOut paper: > Finally, Intel had indicated that microcode updates mitigating the root cause behind CacheOut will be published on June 9th, 2020. We recommend these be installed on all affected Intel platforms to properly mitigate CacheOut. The above blog is indeed dated june 9, however it indicates that the fix was made available, and verified, back in January. I find fault, or at minimum a conflict, between the researchers publication as of june 9, and Intel's statement on the same date. Pretty horrible. I especially dislike that the paper has a section called "Current Status", while the paper is undated as is the norm for academic papers of this type. The "Current Status" isn't 100% clear but appears to be current as of November 2019, so yes this would be in advance of both the June 9 supposed date and the apparent January actual date. Perhaps the paper linked on the sgxaxe website isn't the "updated CacheOut paper" that Intel refers to.