Date: Tue, 9 Jan 2018 00:32:35 +0100
From: Pavel Machek <pavel@ucw.cz>
To: Tim Mouraveiko <tim.ml@ipcopper.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bricked x86 CPU with software?
Message-ID: <20180108233235.GB25349@amd>
References: <5A4D7986.2138.FDC590CF@tim.ml.ipcopper.com>
 <5A50217E.7689.593D738@tim.ml.ipcopper.com>
 <20180106101918.GA22756@amd>
 <5A539529.10290.130FABDC@tim.ml.ipcopper.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
        protocol="application/pgp-signature"; boundary="z6Eq5LdranGa6ru8"
Content-Disposition: inline
In-Reply-To: <5A539529.10290.130FABDC@tim.ml.ipcopper.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org


--z6Eq5LdranGa6ru8
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon 2018-01-08 07:58:33, Tim Mouraveiko wrote:
> > Hi!
> >
> > > > Is the sequence available from ring 3, or does it need ring 0?
> > > >
> > > > Can we get the code? Extraordinary claims and all that...
> > > >
> > >
> > > I did not test privilege level. Are you suggesting that I put the cod=
e out there for everyone to
> > > see or what?
> >
> > Yes, that's what I'm suggesting.
> >
>=20
> That would be neither prudent nor practical.
>=20
> Perhaps you did not consider the consequences. What if it is compatible w=
ith your
> processor? Would you send me a handwritten thank you card if that process=
or stops
> processing? Would you be a happy replacement-sale customer of Intel? I th=
ink you did not
> put much thought into why we are talking about it a year later or at
> all.

Actually, yes, thank you card. Not handwritten -- plenty of CPUs here :-).

> Unlike the now-oh-so-scary feature that was in existence for decades, tha=
t is only so scary
> because of a "clever" idea to "cloud" host different customers on bare me=
tal, without any
> consideration to their security, this could affect real people not just o=
h-so-clever computer
> farmers.

I don't believe you actually have a way to brick CPUs.

Yes, it is possible to brick some computers -- overwriting BIOS will
do the trick, for example; doable from ring 0. There is more firmware
that can be overwritten... That's old news. Worth mentioning on
bugtraq, so manufacturer can fix it, but...

If you had something that worked directly on CPU, that would be news;
and yes, there are fuses there, but I really doubt they can be
manipulated by software. And I believe it would be news worth more
than price of a CPU... Still not exactly dangerous. Usually data are
worth more than hardware.

Ouch, and if it worked from ring 3... That would be newsworthy. That
would be actually quite dangerous. OTOH... people did try to fuzz CPU
instruction sets, so my bet is someone would have noticed.


Best regards,
									Pavel
--=20
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo=
g.html

--z6Eq5LdranGa6ru8
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlpT/5MACgkQMOfwapXb+vLUggCfbpD1psbgl5URlgL9scKFBnAD
G+gAn3oju9rg3A33l6NDCkgGXHImTnnv
=0Jml
-----END PGP SIGNATURE-----

--z6Eq5LdranGa6ru8--