From: Greg KH <gregkh@linuxfoundation.org>
To: Yu Kuai <yukuai1@huaweicloud.com>
Cc: yangerkun@huawei.com, chuck.lever@oracle.com, brauner@kernel.org,
sashal@kernel.org, Coly Li <colyli@suse.de>,
linux-kernel@vger.kernel.org, cve@kernel.org,
"yukuai (C)" <yukuai3@huawei.com>
Subject: Re: CVE-2024-46701: libfs: fix infinite directory reads for offset dir
Date: Tue, 24 Sep 2024 14:13:04 +0200 [thread overview]
Message-ID: <2024092431-valid-psychic-0c7e@gregkh> (raw)
In-Reply-To: <8d0582ae-30f5-aa98-2778-423e81520507@huaweicloud.com>
On Tue, Sep 24, 2024 at 05:44:29PM +0800, Yu Kuai wrote:
> > > On the other hand, v6.6 is affected by this CVE, and this fix can't
> > > be backported to v6.6 because the patchset [1] must be backported first
> > > to expand offset from 32-bit to 64-bit.(This kind of refactor will
> > > break kabi, hence it's not acceptable in our downstream kernels)
> >
> > That's your business decision, and does not affect if we do, or do not,
> > assign a CVE at all. Go work with your management if you wish to change
> > this as it does not pertain to the community in any way.
>
> Yes, I understand, This is just the reason why I tried to close this
> CVE, please ignore this.
>
> BTW, if you still think this CVE is valid, can we bakport the refactor
> patchset to v6.6 as well? I can sent the patches to 6.6 lts, just let me
> know.
Sure, send them on, we are always willing to review potential stable
patches, to the stable@vger.kernel.org list.
thanks,
greg k-h
prev parent reply other threads:[~2024-09-24 12:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b378c634-102f-e115-e925-0a20dc450ff7@huaweicloud.com>
2024-09-24 9:03 ` CVE-2024-46701: libfs: fix infinite directory reads for offset dir Greg KH
2024-09-24 9:44 ` Yu Kuai
2024-09-24 12:13 ` Greg KH [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=2024092431-valid-psychic-0c7e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=brauner@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=colyli@suse.de \
--cc=cve@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=yangerkun@huawei.com \
--cc=yukuai1@huaweicloud.com \
--cc=yukuai3@huawei.com \
/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