Date: Thu, 16 Jun 2022 10:25:19 +0000 From: John Long <codeblue@inbox.lv> To: "freebsd-security@freebsd.org" <freebsd-security@freebsd.org> Subject: Re: Intel CPU CVE Issue: CVE-2022-21166/CVE-2022-21125/CVE-2022-21123 Message-ID: <90e55cbc-a0f7-7220-3759-e05dee2daaf9@inbox.lv> In-Reply-To: <PH0PR19MB4938424C8AD0C148315B26B49EAC9@PH0PR19MB4938.namprd19.prod.outlook.com> References: <PH0PR19MB49384EE776F9B4B73BDDCB719EAC9@PH0PR19MB4938.namprd19.prod.outlook.com> <e2ab3a4a-a0ff-7faa-df82-ce596e7747b5@inbox.lv> <PH0PR19MB4938424C8AD0C148315B26B49EAC9@PH0PR19MB4938.namprd19.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 if Intel gives refunds to people afflicted by their defective products and pays remediation costs to software projects similarly afflicted? Maybe that would give them incentive to do a better job with the junk they're selling. /jl On 16-Jun-22 09:57, Chen, Alvin W wrote: > 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. > >> >> >> [EXTERNAL EMAIL] >> >> 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 CVE issues on FreeBSD? >>> >>> Regards, >>> > > > Internal Use - Confidential
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?90e55cbc-a0f7-7220-3759-e05dee2daaf9>