From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 2FF501A5BAE for ; Sun, 19 Jul 2026 15:40:16 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784475618; cv=none; b=o4IKOO0P/39NtXb7ewvi3E1QhJNgdJshs/H0s/2R5hQeZKdqfXzslPsnfBo5Wbfsr3naKv/fjbrDXEgVqUq6TnGlnEucyemegbFeLQOuqucDeBpwCFA0hth0xu+q/CJDZFFuhDd/6rCwb94fGGxRGqoCVvL02eyMkOhHLH+eQV0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784475618; c=relaxed/simple; bh=n9HRaZOB/8DaZunBmy72e8vAnfYBQTgh7fGYHztccac=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=tXsrQ9u3jWwSXp9ViibsavjD9pXVzub0Z7JlP4gJtBP7g2Yv+ib1laXBGOmsOf3kxGdT4IH7i4nhpAHD4LIrMUQm6jNLvjdQQVvbnSzuFKXmZTOl413+2KXb9gMjj1EHv8kDQBVCyF3hsZZqV2f8UlPRoFUhia1rpft4BquSdTM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=uifum0JH; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="uifum0JH" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 320821F000E9; Sun, 19 Jul 2026 15:40:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1784475616; bh=7/45FbbNPQ/q4NP3Koydb7C9ypM5GngBjdej5uldVVc=; h=From:To:Cc:Subject:Date:Reply-To; b=uifum0JHEOAkM5XBLOCLOT5UuHp6SRme9JhKvu2EZSRI1DOc+fI+B0T3jNE2BiriR d3m3gsYRsYhzHny9BOi7qSSXxSvzVpCGtk87LtTDpExx0ogKy3JAU6JRv6b4KqfQBS lopM10SgqxRlgtlw9vVqBH70E7GncLsRRVupuUJU= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-64016: ksmbd: fix durable reconnect error path file lifetime Date: Sun, 19 Jul 2026 17:37:58 +0200 Message-ID: <2026071900-CVE-2026-64016-577b@gregkh> X-Mailer: git-send-email 2.55.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=2724; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=Pf6cCOcknvWRb4wNc8Ptjk2QGEBn1enCv7Qd0cG49KE=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkx7yMKikQK5fUnmDxbOjn4Yfqi8KxXasFGd75Hlp/wl GR5Ea/fEcvCIMjEICumyPJlG8/R/RWHFL0MbU/DzGFlAhnCwMUpABO5+JdhnoZay/QDLU/u5B/w e/XKvv3yzRczHzEsmGNssC1X8rPatsWh+s7FD5R/FPNlAgA= 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 durable reconnect error path file lifetime After a durable reconnect succeeds, ksmbd_reopen_durable_fd() republishes the same ksmbd_file into the session volatile-id table. If smb2_open() then takes a later error path, cleanup first calls ksmbd_fd_put(work, fp) and then unconditionally calls ksmbd_put_durable_fd(dh_info.fp). In this case fp and dh_info.fp are the same object. The first put drops the reconnect lookup reference, but the final durable put can run __ksmbd_close_fd(NULL, fp). Because the final close is not session-aware, it can free the file object without removing the volatile-id entry that was just published into the session table. Use the session-aware put for the final reconnect drop when the reconnect had already succeeded and the error path is cleaning up the republished file. Earlier reconnect failures, before fp is assigned to dh_info.fp, keep using the durable-only put path. The Linux kernel CVE team has assigned CVE-2026-64016 to this issue. Affected and fixed versions =========================== Issue introduced in 6.18.33 with commit ce2e164c1c51c3f7813b80f8c926836e896bcbb3 and fixed in 6.18.34 with commit a1a39f227c80cbf369767badc32cba2b225147d1 Issue introduced in 7.0.10 with commit 97a0cd55283b4e63fd92804da91c8d9896adcad9 and fixed in 7.0.11 with commit 6cb0b9385320110fe24a5d5ac0000ade4bb3a3f3 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-64016 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/a1a39f227c80cbf369767badc32cba2b225147d1 https://git.kernel.org/stable/c/6cb0b9385320110fe24a5d5ac0000ade4bb3a3f3 https://git.kernel.org/stable/c/3515503322f4819277091839eed46b695096aca5