Received-SPF: pass (google.com: domain of linux-kernel+bounces-209952-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
Precedence: bulk
MIME-Version: 1.0
References: <2024051727-CVE-2023-52666-802b@gregkh> <85948141-5eae-bb3d-cb39-62fc6ddfe476@huawei.com>
In-Reply-To: <85948141-5eae-bb3d-cb39-62fc6ddfe476@huawei.com>
From: Namjae Jeon <linkinjeon@kernel.org>
Date: Tue, 11 Jun 2024 22:28:36 +0900
Message-ID: <CAKYAXd8HNYvhq6jiBUfh3sLwPDEsR43yVkUZuqsX+7ARezy52g@mail.gmail.com>
Subject: Re: CVE-2023-52666: ksmbd: fix potential circular locking issue in smb2_set_ea()
To: Wang Zhaolong <wangzhaolong1@huawei.com>
Cc: cve@kernel.org, linux-kernel@vger.kernel.org, 
	linux-cve-announce@vger.kernel.org, 
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

2024=EB=85=84 6=EC=9B=94 11=EC=9D=BC (=ED=99=94) =EC=98=A4=ED=9B=84 8:30, W=
ang Zhaolong <wangzhaolong1@huawei.com>=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=
=B1:
>
>
> >
> > 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 t=
o
> > the latest release is impossible, the individual changes to resolve thi=
s
> > issue can be found at these commits:
> >       https://git.kernel.org/stable/c/5349fd419e4f685d609c85b781f2b70f0=
fb14848
> >       https://git.kernel.org/stable/c/e61fc656ceeaec65f19a92f0ffbeb562b=
7941e8d
> >       https://git.kernel.org/stable/c/e9ec6665de8f706b4f4133b87b2bd02a1=
59ec57b
> >       https://git.kernel.org/stable/c/ecfd93955994ecc2a1308f5ee4bd90c7f=
ca9a8c6
> >       https://git.kernel.org/stable/c/6fc0a265e1b932e5e97a038f99e29400a=
93baad0
>
> 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.
My bad, I'll update this.
Thank you for your review.
>
> Best regards,
>
> Wang Zhaolong
>