From: Abdifatah Suruur <suruurism@gmail.com>
To: linux-cifs@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linkinjeon@kernel.org,
sfrench@samba.org, senozhatsky@chromium.org, tom@talpey.com
Subject: [PATCH] ksmbd: fix use-after-free of lease table in smb2_lease_break_noti()
Date: Wed, 19 Aug 2026 12:09:05 +0300 [thread overview]
Message-ID: <20260819090905.12448-1-suruurism@gmail.com> (raw)
smb2_lease_break_noti() redirects v2 lease break notifications to the
client lease channel by reading lease->l_lb->conn. The lease table is
linked into the global lease_table_list and destroyed by
destroy_lease_table() on connection teardown, which unlinks it and
kfree()s it under write_lock(&lease_list_lock).
The break path dereferences lease->l_lb and lease->l_lb->conn without
holding lease_list_lock, so when the owning connection is torn down
concurrently (e.g. the client disconnects while another connection's
open triggers a lease break), the table can be freed between the load
and the dereference. This is a use-after-free read of struct
lease_table; the stale conn pointer is then passed to
ksmbd_conn_releasing() and ksmbd_conn_get(), corrupting a refcount on
memory that may have been reallocated.
Take a conn reference and perform the lease-table lookup under
read_lock(&lease_list_lock), matching the lock discipline of
find_same_lease_key() and lookup_lease_in_table(), and transfer the
reference to the async work item instead of re-taking it.
Fixes: 2145945feb2c2 ("ksmbd: route v2 lease breaks on the client lease channel")
Cc: stable@vger.kernel.org
Signed-off-by: Abdifatah Suruur <suruurism@gmail.com>
---
fs/smb/server/oplock.c | 16 +++++++++-------
1 file changed, 9 insertions(+), 7 deletions(-)
diff --git a/fs/smb/server/oplock.c b/fs/smb/server/oplock.c
index 79787099afdc6..ac21583cb6222 100644
--- a/fs/smb/server/oplock.c
+++ b/fs/smb/server/oplock.c
@@ -1007,20 +1007,27 @@ static int smb2_lease_break_noti(struct oplock_info *opinfo, bool wait_ack,
struct lease *lease = opinfo->o_lease;
int ret = 0;
- conn = READ_ONCE(opinfo->conn);
+ conn = ksmbd_conn_get(READ_ONCE(opinfo->conn));
+ read_lock(&lease_list_lock);
if (lease->version == 2 && lease->l_lb && lease->l_lb->conn &&
- !ksmbd_conn_releasing(lease->l_lb->conn))
- conn = lease->l_lb->conn;
+ !ksmbd_conn_releasing(lease->l_lb->conn)) {
+ ksmbd_conn_put(conn);
+ conn = ksmbd_conn_get(lease->l_lb->conn);
+ }
+ read_unlock(&lease_list_lock);
if (!conn)
return ksmbd_invalidate_durable_fd(opinfo->fid);
work = ksmbd_alloc_work_struct();
- if (!work)
+ if (!work) {
+ ksmbd_conn_put(conn);
return -ENOMEM;
+ }
br_info = kmalloc_obj(struct lease_break_info, KSMBD_DEFAULT_GFP);
if (!br_info) {
ksmbd_free_work_struct(work);
+ ksmbd_conn_put(conn);
return -ENOMEM;
}
@@ -1036,7 +1043,7 @@ static int smb2_lease_break_noti(struct oplock_info *opinfo, bool wait_ack,
memcpy(br_info->lease_key, lease->lease_key, SMB2_LEASE_KEY_SIZE);
work->request_buf = (char *)br_info;
- work->conn = ksmbd_conn_get(conn);
+ work->conn = conn;
work->sess = opinfo->sess;
ksmbd_conn_r_count_inc(conn);
next reply other threads:[~2026-08-19 9:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 9:09 Abdifatah Suruur [this message]
2026-08-19 10:37 ` Namjae Jeon
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=20260819090905.12448-1-suruurism@gmail.com \
--to=suruurism@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=senozhatsky@chromium.org \
--cc=sfrench@samba.org \
--cc=tom@talpey.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
all inboxes | Powered by JetHome®