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 C49C93E63BA for ; Fri, 8 May 2026 14:23:12 +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=1778250192; cv=none; b=iqfmXNrqqCai1v27qQNFwZmkPUbYg6mHNvJZXy23Gm3XVPpVqRXBLGbaqiAO4IjIJo7qtMZuks38mQefyI+f4XhrBiSW8n67d/nS9fiXP+8WPtRV45D/7boCEGZ7bz07SDP1rDXcrKru7j6s+uIR+xajjybkVFQvIAl6KL/GCNs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778250192; c=relaxed/simple; bh=TFKVi6Xfa6WgA9YoSeQ+f5I+GK9K4TW1/GLmt52954s=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=gFakuthp3e4VcqoSyMTNxhyTAzLCronfVpsCXGiqL/QhimygXT1UQ2h6/3sT8SPe5j28XA/lJcqPMa9UbLlCC/l/FeVFSYHWurnTLwyFu5EetgDhrhVyqb2N3VcsbxAxUY9L8AuRBaQX599qvTYbE1s9Rvphr8l2aIPNz1X+gAU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=2BAJ4++x; 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="2BAJ4++x" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 22C4CC2BCB0; Fri, 8 May 2026 14:23:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1778250192; bh=TFKVi6Xfa6WgA9YoSeQ+f5I+GK9K4TW1/GLmt52954s=; h=From:To:Cc:Subject:Date:Reply-To:From; b=2BAJ4++xiknM6ZzOqVzl4IC+uV5xikn7MuJ3rEWKzt8DMn4p8PXSb1M38bHfhjMTS FU2RZZbd6BxkaA32yIzERAhfll8EWMUs4G56/d8aJe6mUGtwajwBxGJvdD2A0zrSZR iqBxvFoe6W/1++Vphq47uT5aLHuDYVx8d37GfA1E= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-43379: ksmbd: fix use-after-free in smb_lazy_parent_lease_break_close() Date: Fri, 8 May 2026 16:21:48 +0200 Message-ID: <2026050832-CVE-2026-43379-1808@gregkh> X-Mailer: git-send-email 2.54.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=2773; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=kAVHPhgUGkJ08U2EIY6G4WnaYeleLSlB+pcNWR+bp4s=; b=owGbwMvMwCRo6H6F97bub03G02pJDJl/P+a0MlyYL3uzdfHzIB8TnuJl3vYCIspK6cvqGze2b 44tuyHcEcvCIMjEICumyPJlG8/R/RWHFL0MbU/DzGFlAhnCwMUpABNJfckwh5Pv5Er/rImcDKJ+ Hk5S7hz2/z0kGBZc/vJVc/+JT0FtdZEdlT8Sc098c2EDAA== X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in smb_lazy_parent_lease_break_close() opinfo pointer obtained via rcu_dereference(fp->f_opinfo) is being accessed after rcu_read_unlock() has been called. This creates a race condition where the memory could be freed by a concurrent writer between the unlock and the subsequent pointer dereferences (opinfo->is_lease, etc.), leading to a use-after-free. The Linux kernel CVE team has assigned CVE-2026-43379 to this issue. Affected and fixed versions =========================== Issue introduced in 6.6.32 with commit 27b40b7bfcd121fe13a150ffe11957630cf49246 and fixed in 6.6.130 with commit bf4d66d72e4a9e268c1012c331ce9eaedb5e2086 Issue introduced in 6.9 with commit 5fb282ba4fef8985a5acf2b32681f2ec07732561 and fixed in 6.12.78 with commit 960699317d39f46611f4ebeb69edc567c1f4e6b6 Issue introduced in 6.9 with commit 5fb282ba4fef8985a5acf2b32681f2ec07732561 and fixed in 6.18.19 with commit dbbd328cf58261ca239756fe1c0d10c9518d3399 Issue introduced in 6.9 with commit 5fb282ba4fef8985a5acf2b32681f2ec07732561 and fixed in 6.19.9 with commit b3568347c51c46e2cabc356bc34676df98296619 Issue introduced in 6.9 with commit 5fb282ba4fef8985a5acf2b32681f2ec07732561 and fixed in 7.0 with commit eac3361e3d5dd8067b3258c69615888eb45e9f25 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-2026-43379 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/oplock.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/bf4d66d72e4a9e268c1012c331ce9eaedb5e2086 https://git.kernel.org/stable/c/960699317d39f46611f4ebeb69edc567c1f4e6b6 https://git.kernel.org/stable/c/dbbd328cf58261ca239756fe1c0d10c9518d3399 https://git.kernel.org/stable/c/b3568347c51c46e2cabc356bc34676df98296619 https://git.kernel.org/stable/c/eac3361e3d5dd8067b3258c69615888eb45e9f25