From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6418A56B60 for ; Fri, 17 May 2024 14:01:35 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1715954495; cv=none; b=pYizP5uqnDh5dbc37BFvdKKg0ufz2Simi48a9HstRlVoXxJwY2eJR9HpgvU7+6W6AeyP9wKqTRxm3iEWkzShZYoeoLq+z4Aat5VSZEjIAr8AdfBIXPp9cnwOnn88gIHnxKGEhD/WAVNgkki+pAwoK9YAALfOE+rE7Kb1YWBdnag= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1715954495; c=relaxed/simple; bh=Utuxbdq6zDqpTKCzgZpDnl29lKBVWoCppW9uFVmUIeE=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=tYnXf9PsZzJXOqJFEkGgkaKLKoia8XleKJzF9WXnCTzjzDhtbEw1/lLoA2o4C0obgzr1jUBXNl81LU3SJkXE+CbjaDRGj3gYu32/jxofdDQgW+UMG5P/+5JWzxTOtW61u5IGw8Z38ARrFDC3sju1uhhKakGDUGWiK0oOzZHIR3U= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=glxGO7UL; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="glxGO7UL" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8C27BC2BD10; Fri, 17 May 2024 14:01:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1715954494; bh=Utuxbdq6zDqpTKCzgZpDnl29lKBVWoCppW9uFVmUIeE=; h=From:To:Cc:Subject:Date:Reply-to:From; b=glxGO7ULp6Utcy5ROXL4WA+tE5G/0hnS+NLHTiPQ3rQcCcfzS44SFs6eQlXpRgNlV /3Ca/8OA6ePzvI6JqZk6tcCgHtj6sYQ7m7cXcKGD+0uya6npWS8Cn9kcK3vsfzChQ0 6BfnMXAsHd/5ZgwOqP7JfR12Vu8kSbzC2cpUqba8= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2023-52666: ksmbd: fix potential circular locking issue in smb2_set_ea() Date: Fri, 17 May 2024 16:01:27 +0200 Message-ID: <2024051727-CVE-2023-52666-802b@gregkh> X-Mailer: git-send-email 2.45.1 Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Reply-to: , X-Developer-Signature: v=1; a=openpgp-sha256; l=2038; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=Utuxbdq6zDqpTKCzgZpDnl29lKBVWoCppW9uFVmUIeE=; b=owGbwMvMwCRo6H6F97bub03G02pJDGnuyeYvl8VnbzZdkF+sy5/cynAhoaD24/Q+90NKL56wX lqVU7agI5aFQZCJQVZMkeXLNp6j+ysOKXoZ2p6GmcPKBDKEgYtTACZy8RnDgsmujvMfztKae+rn FaV5548w7825Op9hwbZ2n8NqD3/yfPd+s7ht64s/6X+qPgAA X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit Description =========== In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix potential circular locking issue in smb2_set_ea() smb2_set_ea() can be called in parent inode lock range. So add get_write argument to smb2_set_ea() not to call nested mnt_want_write(). The Linux kernel CVE team has assigned CVE-2023-52666 to this issue. Affected and fixed versions =========================== Fixed in 5.15.149 with commit 5349fd419e4f Fixed in 6.1.76 with commit e61fc656ceea Fixed in 6.6.15 with commit e9ec6665de8f Fixed in 6.7.3 with commit ecfd93955994 Fixed in 6.8 with commit 6fc0a265e1b9 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2023-52666 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: fs/smb/server/smb2pdu.c Mitigation ========== 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