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 7B8003BA232; Fri, 24 Apr 2026 13:44:52 +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=1777038292; cv=none; b=bGwfEbpcCEQ4DUwBROa42Q4Rln6Wt7KFn99FrIyQ3Rb7x+8EsuNKfMy7/XVtOaworeiQrZtytNQhlswdw4ZK1a1OFpc8Ehzp7S5T/SmU5eYDfVu37qK1mp7yg78caU7bcJaBfIpAY2I4P6VQ52x4OWFwREx3sNzf88cTNNwy4+U= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777038292; c=relaxed/simple; bh=BMY7MZKY/xZvIBeiEq+MtT7Z7C6x4ZEvDmfwUPXtCHk=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=dCmvMdGxox9eP6G/Y0Dkn4bWzgyLYbhohz8PbTku3fFn21v6du4bDUJC7KRK+hwYYxU7BEOnt2w5hNsJ1AztPHnZj632yCuYKrr/Wqz/a8HTQJ4eqlfjgUAj9rK1B4R/4w6m8EVYlkuDrUUAA6PAhrFHiDWap4YbNdNwHR7zBcU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=DvXECSIR; 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="DvXECSIR" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 0E971C2BCB6; Fri, 24 Apr 2026 13:44:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1777038292; bh=BMY7MZKY/xZvIBeiEq+MtT7Z7C6x4ZEvDmfwUPXtCHk=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=DvXECSIRbxF1f/F+qY6MKhfqROu7VqQ/06aaKuDB/o4cE5ft21/Fjy5T4aE397a+o r+/LVMROMoB/TG9Z9KxUM3RBu0SpC0F1Eyg+vhwZl0ob6i+6UT3o3FseDsfO5mnpRu gIYa8Mc07EgIlkQUMktRPqXPlVvRpWQTwKHINSEw= From: Greg Kroah-Hartman To: stable@vger.kernel.org Cc: Greg Kroah-Hartman , patches@lists.linux.dev, stable@kernel.org, syzbot+cf7946ab25b21abc4b66@syzkaller.appspotmail.com, Eric Biggers , Chao Yu , Jaegeuk Kim Subject: [PATCH 6.12 15/35] f2fs: fix to avoid memory leak in f2fs_rename() Date: Fri, 24 Apr 2026 15:31:22 +0200 Message-ID: <20260424132414.877016555@linuxfoundation.org> X-Mailer: git-send-email 2.53.0 In-Reply-To: <20260424132411.427029259@linuxfoundation.org> References: <20260424132411.427029259@linuxfoundation.org> User-Agent: quilt/0.69 X-stable: review X-Patchwork-Hint: ignore Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 6.12-stable review patch. If anyone has any objections, please let me know. ------------------ From: Chao Yu commit 3cf11e6f36c170050c12171dd6fd3142711478fc upstream. syzbot reported a f2fs bug as below: BUG: memory leak unreferenced object 0xffff888127f70830 (size 16): comm "syz.0.23", pid 6144, jiffies 4294943712 hex dump (first 16 bytes): 3c af 57 72 5b e6 8f ad 6e 8e fd 33 42 39 03 ff <.Wr[...n..3B9.. backtrace (crc 925f8a80): kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline] slab_post_alloc_hook mm/slub.c:4520 [inline] slab_alloc_node mm/slub.c:4844 [inline] __do_kmalloc_node mm/slub.c:5237 [inline] __kmalloc_noprof+0x3bd/0x560 mm/slub.c:5250 kmalloc_noprof include/linux/slab.h:954 [inline] fscrypt_setup_filename+0x15e/0x3b0 fs/crypto/fname.c:364 f2fs_setup_filename+0x52/0xb0 fs/f2fs/dir.c:143 f2fs_rename+0x159/0xca0 fs/f2fs/namei.c:961 f2fs_rename2+0xd5/0xf20 fs/f2fs/namei.c:1308 vfs_rename+0x7ff/0x1250 fs/namei.c:6026 filename_renameat2+0x4f4/0x660 fs/namei.c:6144 __do_sys_renameat2 fs/namei.c:6173 [inline] __se_sys_renameat2 fs/namei.c:6168 [inline] __x64_sys_renameat2+0x59/0x80 fs/namei.c:6168 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xe2/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f The root cause is in commit 40b2d55e0452 ("f2fs: fix to create selinux label during whiteout initialization"), we added a call to f2fs_setup_filename() without a matching call to f2fs_free_filename(), fix it. Fixes: 40b2d55e0452 ("f2fs: fix to create selinux label during whiteout initialization") Cc: stable@kernel.org Reported-by: syzbot+cf7946ab25b21abc4b66@syzkaller.appspotmail.com Closes: https://lore.kernel.org/linux-f2fs-devel/69a75fe1.a70a0220.b118c.0014.GAE@google.com Suggested-by: Eric Biggers Signed-off-by: Chao Yu Signed-off-by: Jaegeuk Kim Signed-off-by: Greg Kroah-Hartman --- fs/f2fs/namei.c | 1 + 1 file changed, 1 insertion(+) --- a/fs/f2fs/namei.c +++ b/fs/f2fs/namei.c @@ -940,6 +940,7 @@ static int f2fs_rename(struct mnt_idmap return err; err = f2fs_create_whiteout(idmap, old_dir, &whiteout, &fname); + f2fs_free_filename(&fname); if (err) return err; }