From: Greg KH <gregkh@linuxfoundation.org>
To: Bin Lan <bin.lan.cn@windriver.com>
Cc: bin.lan.cn@eng.windriver.com, stable@vger.kernel.org
Subject: Re: [PATCH 6.6] crypto: starfive - Do not free stack buffer
Date: Tue, 3 Dec 2024 09:48:14 +0100 [thread overview]
Message-ID: <2024120328-magnify-brisket-23e4@gregkh> (raw)
In-Reply-To: <1674ed4c-1e86-4d7e-8840-3b7d14f9987c@windriver.com>
On Tue, Dec 03, 2024 at 04:34:25PM +0800, Bin Lan wrote:
>
> On 12/3/2024 4:23 PM, Greg KH wrote:
> > CAUTION: This email comes from a non Wind River email account!
> > Do not click links or open attachments unless you recognize the sender and know the content is safe.
> >
> > On Tue, Dec 03, 2024 at 02:52:13PM +0800, bin.lan.cn@eng.windriver.com wrote:
> > > From: Jia Jie Ho <jiajie.ho@starfivetech.com>
> > >
> > > [ Upstream commit d7f01649f4eaf1878472d3d3f480ae1e50d98f6c ]
> > >
> > > RSA text data uses variable length buffer allocated in software stack.
> > > Calling kfree on it causes undefined behaviour in subsequent operations.
> > >
> > > Cc: <stable@vger.kernel.org> #6.7+
> > The cc: says 6.7 and newer, and yet you are wanting this for 6.6.y?
> > Why? Why ignore what the author asked for?
> >
> > thanks,
> >
> > greg k-h
>
> I want to backport it to fix CVE-2024-39478.
Again, how do you know that that CVE is relevant for kernels older than
6.7.y? Have you tested this? Have you proved that 6.6.y needs this?
If not, there's no way we can take it, nor would you want us to take it,
right?
thanks,
greg k-h
next prev parent reply other threads:[~2024-12-03 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 6:52 [PATCH 6.6] crypto: starfive - Do not free stack buffer bin.lan.cn
2024-12-03 8:23 ` Greg KH
2024-12-03 8:34 ` Bin Lan
2024-12-03 8:48 ` Greg KH [this message]
2024-12-03 18:13 ` Sasha Levin
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=2024120328-magnify-brisket-23e4@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bin.lan.cn@eng.windriver.com \
--cc=bin.lan.cn@windriver.com \
--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