From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Gregory Price <gourry@gourry.net>,
x86@kernel.org, linux-kernel@vger.kernel.org, tglx@linutronix.de,
mingo@redhat.com, dave.hansen@linux.intel.com, hpa@zytor.com,
peterz@infradead.org, mario.limonciello@amd.com,
riel@surriel.com, yazen.ghannam@amd.com, me@mixaill.net,
kai.huang@intel.com, sandipan.das@amd.com, darwi@linutronix.de,
stable@vger.kernel.org
Subject: Re: [PATCH v2] x86/amd: Disable RDSEED on AMD Zen5 because of an error.
Date: Sun, 19 Oct 2025 16:46:06 +0200 [thread overview]
Message-ID: <aPT5rnbfP5efmo4I@zx2c4.com> (raw)
In-Reply-To: <20251018100314.GAaPNl4ngomUnreTbZ@fat_crate.local>
Hi Borislav,
On Sat, Oct 18, 2025 at 12:03:14PM +0200, Borislav Petkov wrote:
> > This was observed on more than 1 Zen5 model, so it should be disabled
> > for all of Zen5 until/unless a comprehensive blacklist can be built.
>
> As I said the last time, we're working on it. Be patient pls.
While your team is checking into this, I'd be most interested to know
one way or the other whether this affects RDRAND too. Since RDRAND uses
the same source as RDSEED for seeding its DRBG, I could imagine it
triggering this bug too (in unlikely circumstances), and then generating
random looking output that's actually based on a key that has some runs
of zeros in it. We'd have a hard time figuring this out from looking at
the output (or even triggering it deliberately), but it seems like
something that should be knowable by the team doing root cause analysis
of the RDSEED bug.
Thanks,
Jason
next prev parent reply other threads:[~2025-10-19 14:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-18 2:40 [PATCH v2] x86/amd: Disable RDSEED on AMD Zen5 because of an error Gregory Price
2025-10-18 10:03 ` Borislav Petkov
2025-10-19 14:46 ` Jason A. Donenfeld [this message]
2025-10-19 15:00 ` Borislav Petkov
2025-10-19 15:03 ` Jason A. Donenfeld
2025-11-03 10:22 ` Christopher Snowhill
2025-11-03 12:03 ` Borislav Petkov
2025-11-03 23:55 ` Christopher Snowhill
2025-11-04 13:21 ` Borislav Petkov
2025-11-04 14:28 ` Jason A. Donenfeld
2025-11-04 15:00 ` Jason A. Donenfeld
2025-11-04 18:08 ` Thiago Macieira
2025-11-04 21:56 ` Jason A. Donenfeld
2025-11-04 23:50 ` Thiago Macieira
2025-11-05 1:58 ` Jason A. Donenfeld
2025-11-05 16:41 ` Thiago Macieira
2025-11-07 19:13 ` Jason A. Donenfeld
2025-11-07 19:55 ` Thiago Macieira
2025-11-07 23:07 ` Jason A. Donenfeld
2025-11-07 23:11 ` Thiago Macieira
2025-11-08 0:04 ` Jason A. Donenfeld
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=aPT5rnbfP5efmo4I@zx2c4.com \
--to=jason@zx2c4.com \
--cc=bp@alien8.de \
--cc=darwi@linutronix.de \
--cc=dave.hansen@linux.intel.com \
--cc=gourry@gourry.net \
--cc=hpa@zytor.com \
--cc=kai.huang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=me@mixaill.net \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=sandipan.das@amd.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yazen.ghannam@amd.com \
/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