From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org, stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
linux-kernel@vger.kernel.org, linkinjeon@kernel.org,
stfrench@microsoft.com, d.ornaghi97@gmail.com,
knavaneeth786@gmail.com, Alva Lan <alvalan9@foxmail.com>
Subject: Re: [PATCH 6.6.y 0/1] ksmbd: validate owner of durable handle on reconnect
Date: Sun, 24 May 2026 08:09:23 -0400 [thread overview]
Message-ID: <20260524-stable-item007-reply@kernel.org> (raw)
In-Reply-To: <tencent_DE479764A6B5230E038C7F4315AD4C0DC606@qq.com>
> This patch backports upstream commit 49110a8ce654 ("ksmbd: validate owner
> of durable handle on reconnect") to the 6.6.y stable branch to address
> CVE-2026-31717.
> [...]
> An additional adaptation was needed for 6.6.y: in ksmbd_free_global_file_table(),
> the call to ksmbd_destroy_file_table(&global_ft) was replaced with
> idr_destroy/kfree, since the function changed to take a
> struct ksmbd_session *. This matches the approach in upstream commit
> d484d621d40f ("ksmbd: add durable scavenger timer").
Thanks for the backport. The 6.12.y version has been queued.
For 6.6.y, the diff isn't a straight cherry-pick and the rewritten
ksmbd_free_global_file_table() path in particular is a non-trivial
stable-only adaptation. Before I queue this for 6.6.y, could you get
Acks from the ksmbd maintainers on the 6.6.y diff specifically? In
particular:
Namjae Jeon <linkinjeon@kernel.org>
Steve French <stfrench@microsoft.com>
Once one of them has Ack'd the 6.6 adaptation I'll pick it up.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-05-24 12:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 11:38 [PATCH 6.6.y 0/1] ksmbd: validate owner of durable handle on reconnect Alva Lan
2026-05-22 11:39 ` [PATCH 6.6.y 1/1] " Alva Lan
2026-05-24 12:09 ` Sasha Levin [this message]
2026-05-24 15:13 ` [PATCH 6.6.y 0/1] " Namjae Jeon
2026-05-25 11:17 ` Alva Lan
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=20260524-stable-item007-reply@kernel.org \
--to=sashal@kernel.org \
--cc=alvalan9@foxmail.com \
--cc=d.ornaghi97@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=knavaneeth786@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=stfrench@microsoft.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