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 242DF39022E for ; Sun, 19 Jul 2026 12:02:27 +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=1784462550; cv=none; b=Mo5U8JwOcsIM67pHZYBYAROHeI0N7D62xvIo9Lk01qkEbncWYHlCvgRBdSKrrSBodrLCoUX0DMP574v76p9V9UxBdPKGqgTA5Jnzt4BKm0Bw1yKLZfh3T7LcdLDFPWm8Ds2M6B9gTngXk4KSem0zglpmsX9RlXmRdYf1NC4S7vk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784462550; c=relaxed/simple; bh=PsHNmFFSiES3YQddDgVeJYm2wyKbn887t7daDIOh0fg=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=fvo6xHZMbTJdbezbo30m2/xaacouWANByPTERL2gw/FUDv0fetG68NdI27k4dgqIMV0+4zlPOoe4VGtbnFAkHK69adNX0Qe5GVxnV2j74VhoiFWNI5llr2JkLlY/bl80EQIiX19m0ep22rxNHyJEIrCMU4cUBQ8QG9SBiiSza3Y= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=RzEDKOCQ; 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="RzEDKOCQ" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 885771F000E9; Sun, 19 Jul 2026 12:02:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1784462547; bh=JTt+2cmUSpM9IYV4SG0x7ohx/bLHsAzHzmHBBhA12F0=; h=From:To:Cc:Subject:Date:Reply-To; b=RzEDKOCQ+b4bMZtvm8BQN4NtOBOxMyl1hYYYKB2PWTmNTaVGme7KlrKd+GvjPZULu wOegGsIJ72BuA+RlVpggUwxJKcK4kuk1Jb2132sTFSVFJbPnvEgvzFm4IEGC4M9nB+ IK1FKNEYPQM5KcDR7qzxKjiG2o/kAP9wWh0t8dCM= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-53399: nfsd: release layout stid on setlease failure Date: Sun, 19 Jul 2026 14:02:05 +0200 Message-ID: <2026071958-CVE-2026-53399-c8aa@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=3873; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=RLi9yZQ2wJ7POeVPhEYlGkifOg37AX8P4eXddFddKPE=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkxe7adYxUXOLs+27NZel/dGpm0t6e0jGYVu9b7O95z3 t3YN6emI5aFQZCJQVZMkeXLNp6j+ysOKXoZ2p6GmcPKBDKEgYtTACbSrc2w4MDpaF777GjlI1zq FmXGT4oCburkMsx3yWeI/BCp9m6OuNqbrXvLPrKqeQcDAA== 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: nfsd: release layout stid on setlease failure nfs4_alloc_stid() publishes the new stid into cl->cl_stateids via idr_alloc_cyclic() under cl_lock before returning to nfsd4_alloc_layout_stateid(). When nfsd4_layout_setlease() then fails, the error path frees the layout stateid directly with kmem_cache_free() without ever calling idr_remove(), leaving the IDR slot pointing at freed slab memory. Any subsequent IDR walker (states_show, client teardown) dereferences the dangling pointer. The correct teardown for an IDR-published stid is nfs4_put_stid(), which removes the IDR slot under cl_lock, dispatches sc_free (nfsd4_free_layout_stateid) to release ls->ls_file via nfsd4_close_layout(), and drops the nfs4_file reference in its tail. A second issue blocks that switch: nfsd4_free_layout_stateid() unconditionally inspects ls->ls_fence_work via delayed_work_pending() under ls_lock, but INIT_DELAYED_WORK(&ls->ls_fence_work, ...) currently runs only after the setlease call. On the setlease-failure path the destructor would touch an uninitialized delayed_work. nfsd4_alloc_layout_stateid() nfs4_alloc_stid() /* idr_alloc_cyclic under cl_lock */ nfsd4_layout_setlease() /* fails */ nfs4_put_stid() nfsd4_free_layout_stateid() delayed_work_pending(&ls->ls_fence_work) /* needs INIT */ nfsd4_close_layout() /* nfsd_file_put(ls->ls_file) */ put_nfs4_file() Fix by hoisting the ls_fenced / ls_fence_delay / INIT_DELAYED_WORK initialization above the nfsd4_layout_setlease() call, and replace the manual nfsd_file_put + put_nfs4_file + kmem_cache_free cleanup with a single nfs4_put_stid(stp). The Linux kernel CVE team has assigned CVE-2026-53399 to this issue. Affected and fixed versions =========================== Issue introduced in 4.0 with commit c5c707f96fc9a6e5a57ca5baac892673270abe3d and fixed in 6.12.96 with commit d369e5edfaaf83a448016e2f1da392b2174be801 Issue introduced in 4.0 with commit c5c707f96fc9a6e5a57ca5baac892673270abe3d and fixed in 6.18.39 with commit 8dee7c278f1c2b5bb80e17a6281c3812fc8b0cdd Issue introduced in 4.0 with commit c5c707f96fc9a6e5a57ca5baac892673270abe3d and fixed in 7.1.3 with commit 83c2b7797742339bb768f83935f7ca33950db138 Issue introduced in 4.0 with commit c5c707f96fc9a6e5a57ca5baac892673270abe3d and fixed in 7.2-rc1 with commit 30d55c8aabb261bc3f427d6b9aae7ef6206063f9 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-53399 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/nfsd/nfs4layouts.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/d369e5edfaaf83a448016e2f1da392b2174be801 https://git.kernel.org/stable/c/8dee7c278f1c2b5bb80e17a6281c3812fc8b0cdd https://git.kernel.org/stable/c/83c2b7797742339bb768f83935f7ca33950db138 https://git.kernel.org/stable/c/30d55c8aabb261bc3f427d6b9aae7ef6206063f9