linux-kernel - Re: [PATCH] x86, CPU, AMD: Add workaround for family 16h, erratum 793

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <52D970F1.3090401@amd.com>
Date:	Fri, 17 Jan 2014 12:05:37 -0600
From:	Aravind Gopalakrishnan <aravind.gopalakrishnan@....com>
To:	"H. Peter Anvin" <hpa@...or.com>, Borislav Petkov <bp@...en8.de>
CC:	Henrique de Moraes Holschuh <hmh@....eng.br>,
	X86 ML <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org>,
	Kim Naru <kim.naru@....com>,
	Sherry Hurwitz <sherry.hurwitz@....com>
Subject: Re: [PATCH] x86, CPU, AMD: Add workaround for family 16h, erratum
 793

On 1/17/2014 11:42 AM, H. Peter Anvin wrote:
>
> Hence the question: did an unfixed BIOS ever make it into a shipping
> production system?  Because if it did, we do have a coverage hole.
>
> 	-hpa
>

Right, and the answer to your question is: there is a *chance* it did.. 
 From internal discussions, I could
gather that the fix went into BIOS code earlier for desktop/mobile 
versions than it did for server versions;

So there is a chance production systems (desktop ones) might never see 
the issue, but server ones will, as
BIOSes spun only from now onwards will have the workaround..

-Aravind.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/