public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Kristof Havasi <havasiefr@gmail.com>
Cc: Sasha Levin <sashal@kernel.org>, stable@vger.kernel.org
Subject: Re: Does v5.4 need CVE-2022-3566 and CVE-2022-3567 patches
Date: Tue, 25 Apr 2023 16:47:39 +0200	[thread overview]
Message-ID: <ZEfoC9UDzniw6mo_@kroah.com> (raw)
In-Reply-To: <CADBnMvgH1H_+WNSdQ=hJp15v4jh0nwFZVkggeiCSWaFHtzORJQ@mail.gmail.com>

On Tue, Apr 25, 2023 at 04:08:30PM +0200, Kristof Havasi wrote:
> Hi there,
> 
> I was evaluating CVE-2022-3567 and CVE-2022-3566 which both
> revolt around load tearing and reference an ancient Kernel commit:
> > Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> 
> I am not sure whether they are applicable to the v5.4.y branch as well.

I do not know, what specific commits are you referring to?  CVEs mean
nothing, they are not valid identifiers, sorry.

And have you tried applying them to the older kernels and testing to see
if they solve any specific issue?

Or better yet, why use the older kernels, why not stick to the most
recent one?  What is preventing you from switching?

thanks,

gre gk-h

  reply	other threads:[~2023-04-25 14:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-25 14:08 Does v5.4 need CVE-2022-3566 and CVE-2022-3567 patches Kristof Havasi
2023-04-25 14:47 ` Greg KH [this message]
2023-04-25 16:27   ` Kristof Havasi
2023-04-25 18:08     ` Greg KH
2023-04-26  9:44       ` Kristof Havasi
2023-04-26 12:53         ` 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=ZEfoC9UDzniw6mo_@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=havasiefr@gmail.com \
    --cc=sashal@kernel.org \
    --cc=stable@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