From: Brendan Jackman <jackmanb@google.com>
To: gregkh@linuxfoundation.org
Cc: cve@kernel.org, gregkh@kernel.org,
linux-cve-announce@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: CVE-2026-46174: x86/CPU/AMD: Prevent improper isolation of shared resources in Zen2's op cache
Date: Tue, 16 Jun 2026 07:54:43 +0000 [thread overview]
Message-ID: <20260616075443.487120-1-jackmanb@google.com> (raw)
In-Reply-To: <2026052828-CVE-2026-46174-e399@gregkh>
Hi Greg,
This is https://nvd.nist.gov/vuln/detail/cve-2025-54518 right? I suppose we
shouldn't have a separate CVE for the kernel patch.
On the other hand I dunno if this actually matters very much.
Cheers,
Brendan
next parent reply other threads:[~2026-06-16 7:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2026052828-CVE-2026-46174-e399@gregkh>
2026-06-16 7:54 ` Brendan Jackman [this message]
2026-06-17 13:54 ` Greg KH
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=20260616075443.487120-1-jackmanb@google.com \
--to=jackmanb@google.com \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.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
Powered by JetHome