From: Ulrich Hecht <uli@fpond.eu>
To: pavel@denx.de
Cc: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
"nobuhiro1.iwamatsu@toshiba.co.jp"
<nobuhiro1.iwamatsu@toshiba.co.jp>
Subject: Re: [cip-dev] Indirect Target Selection (CVE-2024-28956) Re: Request for review for 4.4-st65, 4.4-cip100
Date: Tue, 17 Jun 2025 17:05:25 +0200 (CEST) [thread overview]
Message-ID: <551448465.231192.1750172725438@webmail.strato.de> (raw)
In-Reply-To: <aFFBeZA4Tnlf3d35@duo.ucw.cz>
> On 06/17/2025 12:20 PM CEST Pavel Machek via lists.cip-project.org <pavel=denx.de@lists.cip-project.org> wrote:
> Should we add something like this?
>
[...]
> ---
>
> Document that ITS workarounds are not present in 4.4-cip.
>
> Signed-off-by: Pavel Machek <pavel@denx.de>
>
> diff --git a/KNOWN-BUGS b/KNOWN-BUGS
> index ec2de4aab685e..b268e54bc96e4 100644
> --- a/KNOWN-BUGS
> +++ b/KNOWN-BUGS
> @@ -19,6 +19,10 @@ architectures.
> Random rewrite from 4.9.320 was not backported. We have seen no good
> explanation why it is needed, and it is rather intrusive.
>
> +Workarounds for Intel Indirect Target Selection (CVE-2024-28956) bugs
> +were not backported to 5.10-stable and older, and so are not present
> +in here, either.
> +
I guess that can't hurt. I'll add it.
CU
Uli
prev parent reply other threads:[~2025-06-17 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 16:55 Request for review for 4.4-st65, 4.4-cip100 Ulrich Hecht
2025-06-17 7:15 ` nobuhiro1.iwamatsu
2025-06-17 9:27 ` Pavel Machek
2025-06-17 10:20 ` Indirect Target Selection (CVE-2024-28956) " Pavel Machek
2025-06-17 15:05 ` Ulrich Hecht [this message]
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=551448465.231192.1750172725438@webmail.strato.de \
--to=uli@fpond.eu \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=pavel@denx.de \
/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