linux-kernel - Re: Does srso safe RET mitigation require microcode update?

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] [day] [month] [year] [list]

Message-ID: <20230814125249.GCZNojoW8pC+ToOews@fat_crate.local>
Date:   Mon, 14 Aug 2023 14:52:49 +0200
From:   Borislav Petkov <bp@...en8.de>
To:     Rainer Fiebig <jrf@...lbox.org>
Cc:     Xi Ruoyao <xry111@...111.site>, x86@...nel.org,
        linux-kernel@...r.kernel.org, Ken Moffat <zarniwhoop@...world.com>
Subject: Re: Does srso safe RET mitigation require microcode update?

On Mon, Aug 14, 2023 at 01:21:01PM +0200, Rainer Fiebig wrote:
> OK, thanks.  So I think a reasonable approach for ordinary users would
> be to update to the latest (LTS-) kernel, use the defaults for the
> mitigations and update to the new AGESA when available.

Yap, pretty much.

-- 
Regards/Gruss,
    Boris.

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