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: <b01e8484-17e6-5253-5d83-9d864c66a7f9@assembler.cz>
Date:   Sat, 1 Sep 2018 17:46:24 +0200
From:   Rudolf Marek <r.marek@...embler.cz>
To:     "Hurwitz, Sherry" <sherry.hurwitz@....com>,
        Henrique de Moraes Holschuh <hmh@....eng.br>,
        Ivan Ivanov <qmastery16@...il.com>
Cc:     Josh Boyer <jwboyer@...nel.org>,
        Linux Firmware <linux-firmware@...nel.org>,
        "Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>,
        "Suthikulpanit, Suravee" <Suravee.Suthikulpanit@....com>,
        "Lendacky, Thomas" <Thomas.Lendacky@....com>,
        "Grimm, Jon" <Jon.Grimm@....com>
Subject: Re: [PATCH 1/1] Update AMD cpu microcode for family 15h

Hi Sherry,

Dne 5.6.2018 v 16:27 Hurwitz, Sherry napsal(a):
> Hi Rudolf, I have been investigating the status with the AMD release
> management, but I have not been given approval to publish any other
> microcode.  I have been trying to track down why there might be a
> version in the wild that I have not been given for public publishing.
> It might have come from a BIOS update and not a OS microcode load but

Yes exactly. Why this exists? Is there some technical restriction that will prevent
microcode loading just in Linux? I think it would be beneficial to have at least
the IBPB protection in place via microcode updates.

> I don't have the definitive details on that either.  I will publish
> whatever is released to me as soon as possible.

Any news on this? The family 15h microcode revision provided for Linux is 0x06001119 but I know that 0x0600111f
exists, which provides the IBPB.

Btw I also think that Family 17h (0x00800F11) Linux microcode update has a same problem.

It does not include IBPB support right? It is included in the "BIOS" only microcode revision 0x08001137.

Thanks,
Rudolf

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ