Date: Wed, 13 Jun 2012 17:42:27 -0700 From: Greg Lewis <glewis@eyesbeyond.com> To: Oliver Pinter <oliver.pntr@gmail.com> Cc: freebsd-security@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-12:04.sysret Message-ID: <20120614004227.GA73665@misty.eyesbeyond.com> In-Reply-To: <CAPjTQNGJW4C6=z-79%2Bq9KfUNADq6iQa0kgQVw5wYNTPDkdwMFw@mail.gmail.com> References: <201206121326.q5CDQXca078536@freefall.freebsd.org> <20120613223758.GA72817@misty.eyesbeyond.com> <CAPjTQNGJW4C6=z-79%2Bq9KfUNADq6iQa0kgQVw5wYNTPDkdwMFw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jun 14, 2012 at 02:23:02AM +0200, Oliver Pinter wrote: > On 6/14/12, Greg Lewis <glewis@eyesbeyond.com> wrote: > > On Tue, Jun 12, 2012 at 01:26:33PM +0000, FreeBSD Security Advisories > > wrote: > >> IV. Workaround > >> > >> No workaround is available. > >> > >> However FreeBSD/amd64 running on AMD CPUs is not vulnerable to this > >> particular problem. > >> > >> Systems with 64 bit capable CPUs, but running the 32 bit FreeBSD/i386 > >> kernel are not vulnerable, nor are systems running on different > >> processor architectures. > > > > I found these last two paragraphs a little confusing. Is the correct > > interpretation that FreeBSD/amd64 running on Intel CPUs is the vulnerable > > combination? > > http://www.kb.cert.org/vuls/byvendor?searchview&Query=FIELD+Reference=649219&SearchOrder=4 Thanks :). That was much clearer. -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : glewis@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120614004227.GA73665>