linux-kernel - microcode: You should not be seeing this. Please send the following couple of lines to x86-<at>-kernel.org

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

Message-ID: <CAP1mzZS7=Vpc0wXeD259S02WP2KTHd3CcnwJrKqzxBJTVZ-b_A@mail.gmail.com>
Date: Sun, 9 Mar 2025 18:46:43 -0400
From: Avraham Hollander <anhollander516@...il.com>
To: x86@...nel.org
Cc: linux-kernel@...r.kernel.org
Subject: microcode: You should not be seeing this. Please send the following
 couple of lines to x86-<at>-kernel.org

After upgrading to Linux 6.13.6 (built myself with a tarball from kernel.org)
with the microcode loading patches for the AMD vulnerability, I am getting
the following at the beginning of dmesg output:

microcode: You should not be seeing this. Please send the following couple
of lines to x86-<at>-kernel.org
microcode: CPUID(1).EAX: 0xa50f00, current revision: 0xa500011

Looking at arch/x86/kernel/cpu/microcode, it's triggering the default
condition in the switch statement in need_sha_check(), but I'm not sure
exactly what's being compared to what with cur_rev.

I am running a Ryzen 5 5600G, family 19h, for which patch 0xa500011 is the
latest microcode. My BIOS already applies this version before Linux boots,
so no runtime microcode update is actually needed, but it seems it's trying
anyways?

I have not had an opportunity to update my BIOS+PSP because ASUS has not
released a firmware update for my board (PRIME B550M-A AC) yet. Could that
be related?