From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Wang Zhaolong <wangzhaolong1@huawei.com>
Cc: cve@kernel.org, linux-kernel@vger.kernel.org,
linux-cve-announce@vger.kernel.org
Subject: Re: CVE-2023-52666: ksmbd: fix potential circular locking issue in smb2_set_ea()
Date: Wed, 12 Jun 2024 10:21:20 +0200 [thread overview]
Message-ID: <2024061202-audience-unblessed-c27d@gregkh> (raw)
In-Reply-To: <85948141-5eae-bb3d-cb39-62fc6ddfe476@huawei.com>
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
prev parent reply other threads:[~2024-06-12 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024051727-CVE-2023-52666-802b@gregkh>
2024-06-11 11:30 ` CVE-2023-52666: ksmbd: fix potential circular locking issue in smb2_set_ea() Wang Zhaolong
2024-06-11 13:28 ` Namjae Jeon
2024-06-12 8:21 ` Greg Kroah-Hartman [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=2024061202-audience-unblessed-c27d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangzhaolong1@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