Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <79c179acaa6ec4e1cf112ae2dfce8370694a5089.camel@xry111.site>
Subject: Does srso safe RET mitigation require microcode update?
From:   Xi Ruoyao <xry111@xry111.site>
To:     x86@kernel.org
Cc:     linux-kernel@vger.kernel.org,
        "Borislav Petkov (AMD)" <bp@alien8.de>,
        Rainer Fiebig <jrf@mailbox.org>
Date:   Mon, 14 Aug 2023 17:00:12 +0800
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.48.4 
MIME-Version: 1.0
Precedence: bulk

Hi,

There seems a difference between Documentation/admin-guide/hw-
vuln/srso.rst and the actual behavior.  The documentation says:

   First of all, it is required that the latest microcode be loaded for
   mitigations to be effective.

And:

    * 'Vulnerable: no microcode':
  =20
      The processor is vulnerable, no microcode extending IBPB
      functionality to address the vulnerability has been applied.

Per the text, if there is no firmware update, the system is just
vulnerable.  But on a real Zen 3 system, the spec_rstack_overflow file
contains "Mitigation: safe RET, no microcode".

So we are puzzled now: is this system vulnerable or mitigated?

--=20
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University