From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795035251; b=pOxQA6z748SLNlv7HBY3IrpX4YzbKG3pRUZFV8FnJmdL9/K+DeaUbJOxEYQKLgsV4OYL 138nCD8HaqMXjRh2GCqH/4JQ7e3CDpNJ4Z1z1ijJwnpT62SJaTLAgNyABUdwU9Sqq/b5+ WuwNLHZ3DJpL2pCMRbVbFT6k2HMNCwLB9iCHeDCwLmpFVUPvkRNqPftpq5bFMzmvY1lkb fZHf6rj3SAwyMKBOgTA5mTImmEdKXRbNXgVlG1SYuihuwGEtM+mczGbIVIKGS4yLz3Z9F bmfMXziosMkUBY/wn77URQq1V679SsxKsTKqBTJkuGY7gXIlL98uMQOcLZpv8F+Gcgg== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795035251; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: In-Reply-To:References:User-Agent:X-stable:X-Patchwork-Hint: MIME-Version:Content-Transfer-Encoding; bh=MGxK2mpw6lP4TPxOXAUMG57qZtS+ss32A8x6LD4QIcQ=; b=a+v722OI2OQ2HleVMA7HUcSv+KwVID5tAHfUXTBctfq9OVc+FWb1l/94GE8fse8lph7n Av7pga7Wj3uo8i9PzJemeNlbBsqfWJ0W3BaX12oUUBrxH3LiT3AistyMK7EgT9CTjP90I xJvXm8yECU+EmWyysZrDBuIWOMo/nuE+/gw2mrmzX0El//eMfv1ww78TXMNQlxP56lLmQ I2KWd/HcPil/zMUa09FHQBNSGmpzyhGgEpohwd/6oYNWCDYZSlFX6R/3wrmDGyGLjLb7J BW/XdySQdSMI0ykbh0Ltwz65FP7mx5XjD5UmaPlBu/DmAeUMDW796/+WLzL4Lj80alQ== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=fWWKjVby; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id AEE83606A320; Wed, 18 Nov 2026 20:54:11 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=fWWKjVby Received: by smtp.kernel.org (Postfix) with ESMTPSA id 0FEF01F000C4; Wed, 18 Nov 2026 20:54:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795035251; bh=MGxK2mpw6lP4TPxOXAUMG57qZtS+ss32A8x6LD4QIcQ=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=fWWKjVbyZ6x1XNz+5oBTuT/MhQ/jhxQyZgEXHRiwCodMd7Mbf968EHnFfjmAOjidk Sd2va8cT7z6Z5QS0VNmibKozlfRYXYN7v89N2CA/1EHKoGWpNbVIFHEfeQfzbGpDkd sntDzK/oLB1Al6sKcPI1JWJGV88SL7IkDD26OlO8= From: Greg Kroah-Hartman To: stable@vger.kernel.org Cc: Greg Kroah-Hartman , patches@lists.linux.dev, Yongjun Gwon , Namjae Jeon , Sasha Levin Subject: [PATCH 6.6 0660/3318] ksmbd: serialize directory emptiness checks with readdir Date: Wed, 18 Nov 2026 15:21:22 +0100 Message-ID: <20261118150337.862581023@linuxfoundation.org> X-Mailer: git-send-email 2.56.0 In-Reply-To: <20261118150313.527275416@linuxfoundation.org> References: <20261118150313.527275416@linuxfoundation.org> User-Agent: quilt/0.69 X-stable: review X-Patchwork-Hint: ignore X-Mailing-List: patches@lists.linux.dev List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 6.6-stable review patch. If anyone has any objections, please let me know. ------------------ From: Yongjun Gwon [ Upstream commit 7220980b2423d06a0604516129bfa4cec8a697ae ] SMB2 QUERY_DIRECTORY holds fp->readdir_lock while it calls iterate_dir() on fp->filp. An SMB2 SET_INFO request with FILE_DISPOSITION_INFORMATION can resolve the same FileId and call ksmbd_vfs_empty_dir() on the same filp without that lock. iterate_dir()'s inode read lock permits concurrent readers and does not serialize per-file iterator state. ext4 stores its dx readdir cursor and fname RB tree in file->private_data. Concurrent reset or refill can therefore free a fname node while the other worker still traverses it or retains its RB-tree link, resulting in use-after-free accesses. An authenticated SMB client with list and delete rights on a directory in a writable KSMBD share backed by ext4 can trigger this when the directory takes the dx readdir path. The client overlaps an SMB2 QUERY_DIRECTORY request with an SMB2 SET_INFO request carrying FILE_DISPOSITION_INFORMATION on one live FileId. In one x86_64 SMP KASAN multi-shot guest using ksmbd-for-next at 171df27077fb, the unmodified kernel reported a cross-worker use-after-free before a panic. The first report's access and free stacks show the two request paths directly (trimmed): BUG: KASAN: slab-use-after-free in ext4_htree_store_dirent+0x488/0x550 Read of size 8 by task kworker/2:0/29 Workqueue: ksmbd-io handle_ksmbd_work Call Trace: ext4_htree_store_dirent+0x488/0x550 htree_dirblock_to_tree+0x535/0x990 ext4_htree_fill_tree+0x319/0xba0 ext4_readdir+0x175a/0x2f40 iterate_dir+0x1b6/0x630 smb2_query_dir+0x1003/0x1cc0 Freed by task 279: free_rb_tree_fname+0x67/0xc0 ext4_readdir+0x13a9/0x2f40 iterate_dir+0x1b6/0x630 ksmbd_vfs_empty_dir+0xa2/0x100 smb2_set_info+0x2ffa/0x45d0 Take fp->readdir_lock across the entire emptiness check. This places both iterators over that handle's filp in the same lock domain while preserving the disposition status handling. The exact code change completed a warning-free x86_64 KASAN bzImage build. Tracing three request pairs showed that the two iterate_dir() calls no longer overlapped and the expected statuses were preserved. A further 1,600 reproducer iterations completed with expected statuses and no KASAN report, Oops, or panic. The reproducer and complete guest configuration are available privately to maintainers on request. Fixes: e2f34481b24d ("cifsd: add server-side procedures for SMB3") Cc: stable@vger.kernel.org Assisted-by: LLM Signed-off-by: Yongjun Gwon Signed-off-by: Namjae Jeon [ sashal: Adapted the directory check to the existing condition without the ksmbd_stream_fd() guard. ] Signed-off-by: Sasha Levin --- fs/smb/server/smb2pdu.c | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/fs/smb/server/smb2pdu.c b/fs/smb/server/smb2pdu.c index aaccef2e3f3bb..0f92fb2efc473 100644 --- a/fs/smb/server/smb2pdu.c +++ b/fs/smb/server/smb2pdu.c @@ -6542,6 +6542,7 @@ static int set_file_disposition_info(struct ksmbd_work *work, struct smb2_file_disposition_info *file_info) { struct inode *inode; + int err; if (!(fp->daccess & FILE_DELETE_LE)) { pr_err("no right to delete : 0x%x\n", fp->daccess); @@ -6550,9 +6551,13 @@ static int set_file_disposition_info(struct ksmbd_work *work, inode = file_inode(fp->filp); if (file_info->DeletePending) { - if (S_ISDIR(inode->i_mode) && - ksmbd_vfs_empty_dir(fp) == -ENOTEMPTY) - return -EBUSY; + if (S_ISDIR(inode->i_mode)) { + mutex_lock(&fp->readdir_lock); + err = ksmbd_vfs_empty_dir(fp); + mutex_unlock(&fp->readdir_lock); + if (err == -ENOTEMPTY) + return -EBUSY; + } smb_break_all_levII_oplock(work, fp, 0); ksmbd_set_inode_pending_delete(fp); } else { -- 2.53.0