From: Mikhail Paulyshka <me@mixaill.net>
To: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Cc: Mikhail Paulyshka <me@mixaill.net>
Subject: [PATCH 0/2] x86/rdrand: implement sanity check for RDSEED
Date: Wed, 12 Mar 2025 15:31:28 +0300 [thread overview]
Message-ID: <20250312123130.8290-1-me@mixaill.net> (raw)
On the AMD Cyan Skillfish (Family 0x17 Model 0x47 Stepping 0x0), which
is a Zen2-based APU found on the AMD BC-250 board, there is a situation
where RDRAND works fine, but RDSEED generates FF. This leads to some
applications that use RDSEED to generate random numbers (such as
Qt and KDE) into a nearly unusable state.
Although AMD has fixed the Zen2 RDRAND issues in 2019 with a microcode update,
no such update has been released for the Family 0x17 Model 0x47 core.
This patchset introduces an separate sanity check for RDSEED and hides the
RDSEED and RDRAND from CPUID on AMD platforms in the case of a malfunction.
Mikhail Paulyshka (2):
x86/rdrand: implement sanity check for RDSEED
x86/rdrand: hide RDRAND and RDSEED from CPUID in case of a malfunction
arch/x86/include/asm/archrandom.h | 1 +
arch/x86/include/asm/msr-index.h | 1 +
arch/x86/kernel/cpu/common.c | 1 +
arch/x86/kernel/cpu/rdrand.c | 48 ++++++++++++++++++++++++--
tools/arch/x86/include/asm/msr-index.h | 1 +
5 files changed, 49 insertions(+), 3 deletions(-)
--
2.48.1
next reply other threads:[~2025-03-12 12:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 12:31 Mikhail Paulyshka [this message]
2025-03-12 12:31 ` [PATCH 1/2] " Mikhail Paulyshka
2025-03-12 16:32 ` Borislav Petkov
2025-03-21 6:51 ` kernel test robot
2025-03-12 12:31 ` [PATCH 2/2] x86/rdrand: hide RDRAND and RDSEED from CPUID in case of a malfunction Mikhail Paulyshka
2025-03-12 12:45 ` Borislav Petkov
2025-03-12 13:36 ` Mikhail Paulyshka
2025-03-12 12:40 ` [PATCH 0/2] x86/rdrand: implement sanity check for RDSEED Borislav Petkov
2025-03-12 13:17 ` Mikhail Paulyshka
2025-03-14 8:40 ` Mikhail Paulyshka
2025-03-13 17:32 ` Borislav Petkov
2025-03-14 8:16 ` Mikhail Paulyshka
2025-03-18 20:50 ` Mario Limonciello
2025-03-18 21:40 ` Mikhail Paulyshka
2025-04-14 11:52 ` Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250312123130.8290-1-me@mixaill.net \
--to=me@mixaill.net \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®