From: Adolf Belka <adolf.belka@ipfire.org>
To: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Special register buffer data sampling (CVE-2020-0543) on new mini system
Date: Sat, 27 Sep 2025 15:01:08 +0200 [thread overview]
Message-ID: <450b6b8a-0b44-4908-8e47-2cfed62d49df@ipfire.org> (raw)
Hi All,
Something I noticed. The new mini system is showing "Vulnerable - No microcode" for the "Special register buffer data sampling (CVE-2020-0543)" vulnerability.
However when I go and look at the Intel site for vulnerabilities versus CPU then for the Celeron J series and CVE-2020-0543 it shows Not Affected.
The vulnerability would need the attacker to have local access to the system and be authenticated, which would mean logged in as root so then you would have already lost big time as they could access anything but it just puzzled me why it is shown as Vulnerable. I presume that this comes from info from Intel that is in the kernel.
Regards,
Adolf.
reply other threads:[~2025-09-27 13:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=450b6b8a-0b44-4908-8e47-2cfed62d49df@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.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