From: Andrew Cooper <andrew.cooper3@citrix.com>
To: alex.murray@canonical.com
Cc: bp@alien8.de, dave.hansen@linux.intel.com,
linux-kernel@vger.kernel.org, tglx@linutronix.de, x86@kernel.org
Subject: Re: [RFC][PATCH] x86/cpu/bugs: Consider having old Intel microcode to be a vulnerability
Date: Thu, 14 Nov 2024 02:09:08 +0000 [thread overview]
Message-ID: <55f6d350-27e8-45b9-bd45-db225aea436e@citrix.com> (raw)
In-Reply-To: <87v7wtvty0.fsf@canonical.com>
>> == Microcode Revision Discussion == The microcode versions in the
>> table were generated from the Intel microcode git repo: 29f82f7429c
>> ("microcode-20241029 Release")
> This upstream microcode release only contained an update for a
> functional issue[1] - not any fixes for security issues.
Now I can point at them, see the release notes for 8ac9378a8487
("microcode-20241112 Release").
Note how it's admitting to have fixed security issues silently in prior
drops. If I were you, I wouldn't make assumptions based on what's not
said in the release notes.
I can count on one hand the number of drops in that repo which I know
(or reasonably suspect) to be "functional issues only", but the one you
happened to reference is a fix for "this CPU overvolts itself to an
early grave". Many would consider this a denial of service, against
ones wallet if nothing else.
~Andrew
next prev parent reply other threads:[~2024-11-14 2:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 17:06 Dave Hansen
2024-11-08 23:36 ` Andrew Cooper
2024-11-12 17:15 ` Dave Hansen
2024-11-12 6:37 ` Alex Murray
2024-11-12 15:51 ` Dave Hansen
2024-11-13 3:29 ` Alex Murray
2024-11-13 16:00 ` Dave Hansen
2024-11-13 23:58 ` Alex Murray
2024-11-14 0:37 ` Dave Hansen
2024-11-18 8:35 ` Alex Murray
2024-11-13 9:28 ` Nikolay Borisov
2024-11-14 2:09 ` Andrew Cooper [this message]
2024-11-18 20:02 ` Dave Hansen
2024-11-19 17:45 ` Pawan Gupta
2024-11-19 18:49 ` Dave Hansen
2024-11-19 19:31 ` Pawan Gupta
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=55f6d350-27e8-45b9-bd45-db225aea436e@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=alex.murray@canonical.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--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®