linux-kernel - Re: CVE-2023-52666: ksmbd: fix potential circular locking issue in smb2_set

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: <2024061202-audience-unblessed-c27d@gregkh>
Date: Wed, 12 Jun 2024 10:21:20 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Wang Zhaolong <wangzhaolong1@...wei.com>
Cc: cve@...nel.org, linux-kernel@...r.kernel.org,
	linux-cve-announce@...r.kernel.org
Subject: Re: CVE-2023-52666: ksmbd: fix potential circular locking issue in
 smb2_set_ea()

On Tue, Jun 11, 2024 at 07:30:20PM +0800, Wang Zhaolong wrote:
> 
> > 
> > The Linux kernel CVE team recommends that you update to the latest
> > stable kernel version for this, and many other bugfixes.  Individual
> > changes are never tested alone, but rather are part of a larger kernel
> > release.  Cherry-picking individual commits is not recommended or
> > supported by the Linux kernel community at all.  If however, updating to
> > the latest release is impossible, the individual changes to resolve this
> > issue can be found at these commits:
> > 	https://git.kernel.org/stable/c/5349fd419e4f685d609c85b781f2b70f0fb14848
> > 	https://git.kernel.org/stable/c/e61fc656ceeaec65f19a92f0ffbeb562b7941e8d
> > 	https://git.kernel.org/stable/c/e9ec6665de8f706b4f4133b87b2bd02a159ec57b
> > 	https://git.kernel.org/stable/c/ecfd93955994ecc2a1308f5ee4bd90c7fca9a8c6
> > 	https://git.kernel.org/stable/c/6fc0a265e1b932e5e97a038f99e29400a93baad0
> 
> Hello.
> 
> Is this a valid CVE patch?
> 
> I noticed that the introduced `get_write` is not being used within the
> function, and there are no follow-up patches addressing this.

Yeah, that's odd.  No, it's not, I'll go revoke this now, thanks for
noticing!

greg k-h