Intel CPU CVE Issue: CVE-2022-21166/CVE-2022-21125/CVE-2022-21123

2022-06-16 Thread Chen, Alvin W
Hi community, Are there any fixes available to fix this Intel CPU CVE issues on FreeBSD? Regards, Alvin Chen Dell | Comercial Client Group office +86-10-82862506, fax +86-10-82861554, Dell Lync 8672506 weike_c...@dell.com Internal Use - Confidential

Re: Intel CPU CVE Issue: CVE-2022-21166/CVE-2022-21125/CVE-2022-21123

2022-06-16 Thread John Long
Does Intel fund OS and application level mitigations of their never-ending failure to design or implement anything properly? It's hard to understand why the victims should pay... /jl On 16-Jun-22 07:51, Chen, Alvin W wrote: Hi community, Are there any fixes available to fix this Intel CPU CV

RE: Intel CPU CVE Issue: CVE-2022-21166/CVE-2022-21125/CVE-2022-21123

2022-06-16 Thread Chen, Alvin W
Intel provides the migration guideline, please refer to : https://www.intel.com/content/www/us/en/developer/articles/technical/software-security-guidance/technical-documentation/processor-mmio-stale-data-vulnerabilities.html It looks like Linux (Ubuntu&Rehat&Suse) and Window are ready. > > > [

Re: Intel CPU CVE Issue: CVE-2022-21166/CVE-2022-21125/CVE-2022-21123

2022-06-16 Thread John Long
1st of all, my comment was because of your post but was not directed at you. Sorry if that was unclear. 2nd of all, great that they give advice. Not so great that people have to actually do the work. This costs everybody *besides Intel* a lot of money and there is no end in sight. How about

RE: Intel CPU CVE Issue: CVE-2022-21166/CVE-2022-21125/CVE-2022-21123

2022-06-16 Thread Chen, Alvin W
It is the situation that the whole FreeBSD community facing: the lack of supporting from vendors, not only for Intel. Many new HW features, like modern standby, Hybrid CPU, new chipsets drivers, need be done by vendors but FreeBSD community need do it. FreeBSD community need influence HW vendors