Date: Thu, 16 Jun 2022 09:57:53 +0000 From: "Chen, Alvin W" <Weike.Chen@Dell.com> To: John Long <codeblue@inbox.lv>, "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: <PH0PR19MB4938424C8AD0C148315B26B49EAC9@PH0PR19MB4938.namprd19.prod.outlook.com> In-Reply-To: <e2ab3a4a-a0ff-7faa-df82-ce596e7747b5@inbox.lv> References: <PH0PR19MB49384EE776F9B4B73BDDCB719EAC9@PH0PR19MB4938.namprd19.prod.outlook.com> <e2ab3a4a-a0ff-7faa-df82-ce596e7747b5@inbox.lv>
index | next in thread | previous in thread | raw e-mail
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 - Confidentialhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?PH0PR19MB4938424C8AD0C148315B26B49EAC9>