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 2/2] x86/rdrand: hide RDRAND and RDSEED from CPUID in case of a malfunction
Date: Wed, 12 Mar 2025 15:31:30 +0300 [thread overview]
Message-ID: <20250312123130.8290-3-me@mixaill.net> (raw)
In-Reply-To: <20250312123130.8290-1-me@mixaill.net>
Some applications use the CPUID call instead of /proc/cpuinfo to get
CPU capabilities. In this case, they will still try to use non-functional
RDRAND/RDSEED implementations.
Disables visibility of RDRAND and RDSEED on AMD platforms.
Signed-off-by: Mikhail Paulyshka <me@mixaill.net>
---
arch/x86/include/asm/msr-index.h | 1 +
arch/x86/kernel/cpu/rdrand.c | 5 +++++
tools/arch/x86/include/asm/msr-index.h | 1 +
3 files changed, 7 insertions(+)
diff --git a/arch/x86/include/asm/msr-index.h b/arch/x86/include/asm/msr-index.h
index 72765b2fe0d8..bc5ef95cf0cb 100644
--- a/arch/x86/include/asm/msr-index.h
+++ b/arch/x86/include/asm/msr-index.h
@@ -614,6 +614,7 @@
#define MSR_AMD64_OSVW_STATUS 0xc0010141
#define MSR_AMD_PPIN_CTL 0xc00102f0
#define MSR_AMD_PPIN 0xc00102f1
+#define MSR_AMD64_CPUID_FN_7 0xc0011002
#define MSR_AMD64_CPUID_FN_1 0xc0011004
#define MSR_AMD64_LS_CFG 0xc0011020
#define MSR_AMD64_DC_CFG 0xc0011022
diff --git a/arch/x86/kernel/cpu/rdrand.c b/arch/x86/kernel/cpu/rdrand.c
index e9f7ef5dfe25..031c4297a54a 100644
--- a/arch/x86/kernel/cpu/rdrand.c
+++ b/arch/x86/kernel/cpu/rdrand.c
@@ -11,6 +11,7 @@
#include <asm/processor.h>
#include <asm/archrandom.h>
#include <asm/sections.h>
+#include <asm/msr.h>
enum { SAMPLES = 8, MIN_CHANGE = 5 };
@@ -46,6 +47,8 @@ void x86_init_rdrand(struct cpuinfo_x86 *c)
if (failure) {
clear_cpu_cap(c, X86_FEATURE_RDRAND);
+ if (c->x86_vendor == X86_VENDOR_AMD || c->x86_vendor == X86_VENDOR_HYGON)
+ msr_clear_bit(MSR_AMD64_CPUID_FN_1, 62);
pr_emerg("RDRAND is not reliable on this platform; disabling.\n");
}
}
@@ -82,6 +85,8 @@ void x86_init_rdseed(struct cpuinfo_x86 *c)
if (failure) {
clear_cpu_cap(c, X86_FEATURE_RDSEED);
+ if (c->x86_vendor == X86_VENDOR_AMD || c->x86_vendor == X86_VENDOR_HYGON)
+ msr_clear_bit(MSR_AMD64_CPUID_FN_7, 18);
pr_emerg("RDSEED is not reliable on this platform; disabling.\n");
}
}
diff --git a/tools/arch/x86/include/asm/msr-index.h b/tools/arch/x86/include/asm/msr-index.h
index 3ae84c3b8e6d..3deb6c11f134 100644
--- a/tools/arch/x86/include/asm/msr-index.h
+++ b/tools/arch/x86/include/asm/msr-index.h
@@ -612,6 +612,7 @@
#define MSR_AMD64_OSVW_STATUS 0xc0010141
#define MSR_AMD_PPIN_CTL 0xc00102f0
#define MSR_AMD_PPIN 0xc00102f1
+#define MSR_AMD64_CPUID_FN_7 0xc0011002
#define MSR_AMD64_CPUID_FN_1 0xc0011004
#define MSR_AMD64_LS_CFG 0xc0011020
#define MSR_AMD64_DC_CFG 0xc0011022
--
2.48.1
next prev parent 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 [PATCH 0/2] x86/rdrand: implement sanity check for RDSEED Mikhail Paulyshka
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 ` Mikhail Paulyshka [this message]
2025-03-12 12:45 ` [PATCH 2/2] x86/rdrand: hide RDRAND and RDSEED from CPUID in case of a malfunction 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-3-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®