linux-kernel - Re: CVE-2024-46701: libfs: fix infinite directory reads for offset dir

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2024092431-valid-psychic-0c7e@gregkh>
Date: Tue, 24 Sep 2024 14:13:04 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Yu Kuai <yukuai1@...weicloud.com>
Cc: yangerkun@...wei.com, chuck.lever@...cle.com, brauner@...nel.org,
	sashal@...nel.org, Coly Li <colyli@...e.de>,
	linux-kernel@...r.kernel.org, cve@...nel.org,
	"yukuai (C)" <yukuai3@...wei.com>
Subject: Re: CVE-2024-46701: libfs: fix infinite directory reads for offset
 dir

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@...r.kernel.org list.

thanks,

greg k-h