From: Wang Zhaolong <wangzhaolong1@huawei.com>
To: <cve@kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-cve-announce@vger.kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: CVE-2023-52666: ksmbd: fix potential circular locking issue in smb2_set_ea()
Date: Tue, 11 Jun 2024 19:30:20 +0800 [thread overview]
Message-ID: <85948141-5eae-bb3d-cb39-62fc6ddfe476@huawei.com> (raw)
In-Reply-To: <2024051727-CVE-2023-52666-802b@gregkh>
>
> 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.
Best regards,
Wang Zhaolong
next prev parent reply other threads:[~2024-06-11 11:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 14:01 CVE-2023-52666: ksmbd: fix potential circular locking issue in smb2_set_ea() Greg Kroah-Hartman
2024-06-11 11:30 ` Wang Zhaolong [this message]
2024-06-11 13:28 ` Namjae Jeon
2024-06-12 8:21 ` Greg Kroah-Hartman
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=85948141-5eae-bb3d-cb39-62fc6ddfe476@huawei.com \
--to=wangzhaolong1@huawei.com \
--cc=cve@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.