* Re: CVE-2023-52666: ksmbd: fix potential circular locking issue in smb2_set_ea() [not found] <2024051727-CVE-2023-52666-802b@gregkh> @ 2024-06-11 11:30 ` Wang Zhaolong 2024-06-11 13:28 ` Namjae Jeon 2024-06-12 8:21 ` Greg Kroah-Hartman 0 siblings, 2 replies; 3+ messages in thread From: Wang Zhaolong @ 2024-06-11 11:30 UTC (permalink / raw) To: cve, linux-kernel, linux-cve-announce; +Cc: Greg Kroah-Hartman > > 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 ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: CVE-2023-52666: ksmbd: fix potential circular locking issue in smb2_set_ea() 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 1 sibling, 0 replies; 3+ messages in thread From: Namjae Jeon @ 2024-06-11 13:28 UTC (permalink / raw) To: Wang Zhaolong; +Cc: cve, linux-kernel, linux-cve-announce, Greg Kroah-Hartman 2024년 6월 11일 (화) 오후 8:30, Wang Zhaolong <wangzhaolong1@huawei.com>님이 작성: > > > > > > 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. My bad, I'll update this. Thank you for your review. > > Best regards, > > Wang Zhaolong > ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: CVE-2023-52666: ksmbd: fix potential circular locking issue in smb2_set_ea() 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 1 sibling, 0 replies; 3+ messages in thread From: Greg Kroah-Hartman @ 2024-06-12 8:21 UTC (permalink / raw) To: Wang Zhaolong; +Cc: cve, linux-kernel, linux-cve-announce 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 ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-06-12 8:21 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[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 is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox
Powered by JetHome