Date: Thu, 04 Jan 2018 03:35:24 +0100 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: "David M. Syzdek" <david.syzdek@acsalaska.net> Cc: Eric van Gyzen <vangyzen@FreeBSD.org>, "freebsd-security\@freebsd.org" <freebsd-security@freebsd.org>, "Ronald F. Guilmette" <rfg@tristatelogic.com> Subject: Re: Intel hardware bug Message-ID: <867esy2vwz.fsf@desk.des.no> In-Reply-To: <7C58A6DB-0760-4E5A-B65D-2ED6A6B7AAD2@acsalaska.net> (David M. Syzdek's message of "Wed, 3 Jan 2018 13:43:08 -0900") References: <19097.1515012519@segfault.tristatelogic.com> <02563ce4-437c-ab96-54bb-a8b591900ba0@FreeBSD.org> <7C58A6DB-0760-4E5A-B65D-2ED6A6B7AAD2@acsalaska.net>
next in thread | previous in thread | raw e-mail | index | archive | help
"David M. Syzdek" <david.syzdek@acsalaska.net> writes: > They did not say it is *NOT* a bug, just that it is not a bug unique > to Intel. [...] Additionally, they indirectly imply that both AMD and > ARM chips are affected by the same bug, however this is, at least in > AMD’s case, appears to be directly refuted [...] by AMD: There are three different issues. One of them (CVE-2017-5754, labeled “Meltdown”) is easily mitigated and has so far only been shown to affect Intel processors. The other two (CVE-2017-5753 and CVE-2017-5715, collectively labeled “Spectre”) affect AMD and ARM processors as well and have no known workaround. So far, it has been shown that an unprivileged process can read data from the kernel (Meltdown) and other processes (Spectre), and that a privileged process in a VM can read data from the host and presumably also from other VMs on the same host (Spectre). DES -- Dag-Erling Smørgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?867esy2vwz.fsf>