linux-kernel - Re: [PATCH 1/2] x86/microcode/AMD: Load late on both threads too

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]

Date:   Thu, 17 Aug 2023 17:40:44 +0200
From:   Borislav Petkov <bp@...en8.de>
To:     Jim Mattson <jmattson@...gle.com>
Cc:     dave.hansen@...el.com, linux-kernel@...r.kernel.org,
        stable@...nel.org, x86@...nel.org
Subject: Re: [PATCH 1/2] x86/microcode/AMD: Load late on both threads too

On Wed, Aug 16, 2023 at 03:37:20PM -0700, Jim Mattson wrote:
> SEV-SNP is supposed to protect the guest from a malicious host. A
> malicious host may not load the microcode update on both threads. As a
> result, it gives me some concern when I see something like this
> (https://lore.kernel.org/lkml/20230808190239.131508-1-john.allen@amd.com/):

All I can say is that if this is needed for a SEV/SNP-relevant fix, the
attestation flow will be adjusted to handle this properly.

> I had assumed that the SEV-SNP microcode revision attestation was for
> all logical processors on the host. Are you saying that it is not?

The attestation flow is fine as it takes into account the lowest
microcode revision across all cores in the system. So it doesn't matter
for SNP which core has been applied successfully or which one hasn't.

HTH.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette