From: Chao Yu <chao@kernel.org>
To: Gao Xiang <hsiangkao@linux.alibaba.com>, linux-erofs@lists.ozlabs.org
Cc: chao@kernel.org, LKML <linux-kernel@vger.kernel.org>,
Yuhao Jiang <danisjiang@gmail.com>,
Junrui Luo <moonafterrain@outlook.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v3] erofs: fix the out-of-bounds nameoff handling for trailing dirents
Date: Tue, 21 Apr 2026 15:26:50 +0800 [thread overview]
Message-ID: <b9d787ce-9020-4140-8d13-23a20809976d@kernel.org> (raw)
In-Reply-To: <20260416094408.3466613-1-hsiangkao@linux.alibaba.com>
On 4/16/2026 5:44 PM, Gao Xiang wrote:
> Currently we already have boundary-checks for nameoffs, but the trailing
> dirents are special since the namelens are calculated with strnlen()
> with unchecked nameoffs.
>
> If a crafted EROFS has a trailing dirent with nameoff >= maxsize,
> maxsize - nameoff can underflow, causing strnlen() to read past the
> directory block.
>
> nameoff0 should also be verified to be a multiple of
> `sizeof(struct erofs_dirent)` as well [1].
>
> [1] https://sashiko.dev/#/patchset/20260416063511.3173774-1-hsiangkao%40linux.alibaba.com
> Fixes: 3aa8ec716e52 ("staging: erofs: add directory operations")
> Fixes: 33bac912840f ("staging: erofs: keep corrupted fs from crashing kernel in erofs_readdir()")
> Reported-by: Yuhao Jiang <danisjiang@gmail.com>
> Reported-by: Junrui Luo <moonafterrain@outlook.com>
> Closes: https://lore.kernel.org/r/A0FD7E0F-7558-49B0-8BC8-EB1ECDB2479A@outlook.com
> Cc: stable@vger.kernel.org
> Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>
> ---
> v3:
> - Disallow unaligned nameoff0 to avoid petential oob reads as well.
>
> fs/erofs/dir.c | 29 ++++++++++++++++-------------
> 1 file changed, 16 insertions(+), 13 deletions(-)
>
> diff --git a/fs/erofs/dir.c b/fs/erofs/dir.c
> index e5132575b9d3..d074fded1577 100644
> --- a/fs/erofs/dir.c
> +++ b/fs/erofs/dir.c
> @@ -19,20 +19,18 @@ static int erofs_fill_dentries(struct inode *dir, struct dir_context *ctx,
> const char *de_name = (char *)dentry_blk + nameoff;
> unsigned int de_namelen;
>
> - /* the last dirent in the block? */
> - if (de + 1 >= end)
> - de_namelen = strnlen(de_name, maxsize - nameoff);
> - else
> + /* non-trailing dirent in the directory block? */
> + if (de + 1 < end)
> de_namelen = le16_to_cpu(de[1].nameoff) - nameoff;
> + else if (maxsize <= nameoff)
> + goto err_bogus;
> + else
> + de_namelen = strnlen(de_name, maxsize - nameoff);
>
> - /* a corrupted entry is found */
> - if (nameoff + de_namelen > maxsize ||
> - de_namelen > EROFS_NAME_LEN) {
> - erofs_err(dir->i_sb, "bogus dirent @ nid %llu",
> - EROFS_I(dir)->nid);
> - DBG_BUGON(1);
> - return -EFSCORRUPTED;
> - }
> + /* a corrupted entry is found (including negative namelen) */
> + if (!in_range32(de_namelen, 1, EROFS_NAME_LEN) ||
> + nameoff + de_namelen > maxsize)
> + goto err_bogus;
>
> if (!dir_emit(ctx, de_name, de_namelen,
> erofs_nid_to_ino64(EROFS_SB(dir->i_sb),
> @@ -42,6 +40,10 @@ static int erofs_fill_dentries(struct inode *dir, struct dir_context *ctx,
> ctx->pos += sizeof(struct erofs_dirent);
> }
> return 0;
> +err_bogus:
> + erofs_err(dir->i_sb, "bogus dirent @ nid %llu", EROFS_I(dir)->nid);
> + DBG_BUGON(1);
> + return -EFSCORRUPTED;
> }
>
> static int erofs_readdir(struct file *f, struct dir_context *ctx)
> @@ -88,7 +90,8 @@ static int erofs_readdir(struct file *f, struct dir_context *ctx)
> }
>
> nameoff = le16_to_cpu(de->nameoff);
> - if (nameoff < sizeof(struct erofs_dirent) || nameoff >= bsz) {
You mean?
if (!nameoff || nameoff >= bsz || nameoff % sizeof(struct erofs_dirent))
Thanks,
> + if (nameoff < sizeof(struct erofs_dirent) || nameoff >= bsz ||
> + (nameoff % sizeof(struct erofs_dirent))) {
> erofs_err(sb, "invalid de[0].nameoff %u @ nid %llu",
> nameoff, EROFS_I(dir)->nid);
> err = -EFSCORRUPTED;
next prev parent reply other threads:[~2026-04-21 7:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 6:03 [PATCH] erofs: fix the out-of-bounds nameoff handling for trailing dirents Gao Xiang
2026-04-16 6:35 ` [PATCH v2] " Gao Xiang
2026-04-16 9:44 ` [PATCH v3] " Gao Xiang
2026-04-21 7:26 ` Chao Yu [this message]
2026-04-21 7:38 ` Gao Xiang
2026-04-21 8:31 ` Chao Yu
2026-04-21 7:59 ` [PATCH v4] " Gao Xiang
2026-04-21 8:32 ` Chao Yu
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=b9d787ce-9020-4140-8d13-23a20809976d@kernel.org \
--to=chao@kernel.org \
--cc=danisjiang@gmail.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=moonafterrain@outlook.com \
--cc=stable@vger.kernel.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