From: Vasiliy Kovalev <kovalev@altlinux.org>
To: Jan Kara <jack@suse.com>, Andrew Morton <akpm@osdl.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
linux-ext4@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, lvc-project@linuxtesting.org,
kovalev@altlinux.org
Subject: [PATCH 1/2] ext2: validate i_nlink before decrement in ext2_unlink()
Date: Thu, 2 Apr 2026 01:08:36 +0300 [thread overview]
Message-ID: <20260401220837.2424925-2-kovalev@altlinux.org> (raw)
In-Reply-To: <20260401220837.2424925-1-kovalev@altlinux.org>
A crafted ext2 image can provide a directory entry pointing to an inode
with i_links_count == 0 on disk. Calling unlink() on such an entry
triggers WARN_ON inside drop_nlink():
WARNING: CPU: 3 PID: 609 at fs/inode.c:336 drop_nlink+0xad/0xd0 fs/inode.c:336
CPU: 3 UID: 0 PID: 609 Comm: syz-executor Not tainted 6.12.77+ #1
Call Trace:
<TASK>
inode_dec_link_count include/linux/fs.h:2518 [inline]
ext2_unlink+0x26c/0x300 fs/ext2/namei.c:295
vfs_unlink+0x2fc/0x9b0 fs/namei.c:4477
do_unlinkat+0x53e/0x730 fs/namei.c:4541
__do_sys_unlink fs/namei.c:4589 [inline]
__se_sys_unlink fs/namei.c:4587 [inline]
__x64_sys_unlink+0xc6/0x110 fs/namei.c:4587
do_syscall_x64 arch/x86/entry/common.c:47 [inline]
do_syscall_64+0xf5/0x220 arch/x86/entry/common.c:78
entry_SYSCALL_64_after_hwframe+0x77/0x7f
</TASK>
At the point of the crash, ext2_delete_entry() has already committed
the removal of the directory entry to disk, so returning an error is
not an option. Instead, skip the decrement and report the corruption
via ext2_error(), which marks the superblock as having errors. The
inode will be reclaimed when its last reference is dropped.
Found by Linux Verification Center (linuxtesting.org) with Syzkaller.
Cc: stable@vger.kernel.org
Fixes: a513b035eadf ("[PATCH] ext2: switch to inode_inc_count, inode_dec_count")
Signed-off-by: Vasiliy Kovalev <kovalev@altlinux.org>
---
fs/ext2/namei.c | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/fs/ext2/namei.c b/fs/ext2/namei.c
index bde617a66cec..ea49e8f2b292 100644
--- a/fs/ext2/namei.c
+++ b/fs/ext2/namei.c
@@ -293,7 +293,12 @@ static int ext2_unlink(struct inode *dir, struct dentry *dentry)
goto out;
inode_set_ctime_to_ts(inode, inode_get_ctime(dir));
- inode_dec_link_count(inode);
+ if (!inode->i_nlink)
+ ext2_error(inode->i_sb, __func__,
+ "inode %lu has zero i_nlink on unlink, fs may be corrupt",
+ inode->i_ino);
+ else
+ inode_dec_link_count(inode);
err = 0;
out:
return err;
--
2.50.1
next prev parent reply other threads:[~2026-04-01 22:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 22:08 [PATCH 0/2] ext2: fix WARN_ON in drop_nlink() triggered by corrupt images Vasiliy Kovalev
2026-04-01 22:08 ` Vasiliy Kovalev [this message]
2026-04-01 22:08 ` [PATCH 2/2] ext2: guard against zero i_nlink on new_inode in ext2_rename() Vasiliy Kovalev
2026-04-04 15:27 ` [PATCH 0/2] ext2: fix WARN_ON in drop_nlink() triggered by corrupt images Vasiliy Kovalev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260401220837.2424925-2-kovalev@altlinux.org \
--to=kovalev@altlinux.org \
--cc=adobriyan@gmail.com \
--cc=akpm@osdl.org \
--cc=jack@suse.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox