Linux EXT4 FS development
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: linux-ext4@vger.kernel.org
Cc: tytso@mit.edu, sandeen@redhat.com, agruenba@redhat.com
Subject: [PATCH 2/8] e2fsck: fix extended attribute block checking
Date: Thu, 24 Sep 2026 17:23:36 -0500	[thread overview]
Message-ID: <20260924222944.3683556-3-sandeen@redhat.com> (raw)
In-Reply-To: <20260924222944.3683556-1-sandeen@redhat.com>

From: Andreas Gruenbacher <agruenba@redhat.com>

Fix the same problems as in check_ea_in_inode().

The 'entry->e_value_offs + entry->e_value_size > fs->blocksize' check is
covered by the region_allocate() check that follows it, so it can be
removed.

Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
 e2fsck/pass1.c | 19 ++++++++++++++-----
 1 file changed, 14 insertions(+), 5 deletions(-)

diff --git a/e2fsck/pass1.c b/e2fsck/pass1.c
index 555429b6..f66a2908 100644
--- a/e2fsck/pass1.c
+++ b/e2fsck/pass1.c
@@ -2493,6 +2493,7 @@ static int check_ext_attr(e2fsck_t ctx, struct problem_context *pctx,
 	char *		end;
 	struct ext2_ext_attr_header *header;
 	struct ext2_ext_attr_entry *first, *entry;
+	unsigned int	remain;
 	blk64_t		quota_blocks = EXT2FS_C2B(fs, 1);
 	__u64		quota_inodes = 0;
 	region_t	region = 0;
@@ -2630,10 +2631,19 @@ static int check_ext_attr(e2fsck_t ctx, struct problem_context *pctx,
 
 	first = (struct ext2_ext_attr_entry *)(header+1);
 	end = block_buf + fs->blocksize;
+	/* take finish entry 0UL into account */
+	remain = end - (char *)first - sizeof(__u32);
 	entry = first;
-	while ((char *)entry < end && *(__u32 *)entry) {
+	while (!EXT2_EXT_IS_LAST_ENTRY(entry)) {
 		__u32 hash;
 
+		/* entry->e_name_len is within the first four bytes */
+		if (EXT2_EXT_ATTR_LEN(entry->e_name_len) > remain) {
+			if (fix_problem(ctx, PR_1_EA_BAD_NAME, pctx))
+				goto clear_extattr;
+			break;
+		}
+		remain -= EXT2_EXT_ATTR_LEN(entry->e_name_len);
 		if (region_allocate(region, (char *)entry - (char *)header,
 			           EXT2_EXT_ATTR_LEN(entry->e_name_len))) {
 			if (fix_problem(ctx, PR_1_EA_ALLOC_COLLISION, pctx))
@@ -2649,13 +2659,12 @@ static int check_ext_attr(e2fsck_t ctx, struct problem_context *pctx,
 			break;
 		}
 		if (entry->e_value_inum == 0) {
-			if (entry->e_value_size > EXT2_XATTR_SIZE_MAX ||
-			    (entry->e_value_offs + entry->e_value_size >
-			     fs->blocksize)) {
+			if (EXT2_EXT_ATTR_SIZE(entry->e_value_size) > remain) {
 				if (fix_problem(ctx, PR_1_EA_BAD_VALUE, pctx))
 					goto clear_extattr;
 				break;
 			}
+			remain -= EXT2_EXT_ATTR_SIZE(entry->e_value_size);
 			if (entry->e_value_size &&
 			    region_allocate(region, entry->e_value_offs,
 					    EXT2_EXT_ATTR_SIZE(entry->e_value_size))) {
@@ -2697,7 +2706,7 @@ static int check_ext_attr(e2fsck_t ctx, struct problem_context *pctx,
 
 		entry = EXT2_EXT_ATTR_NEXT(entry);
 	}
-	if (region_allocate(region, (char *)entry - (char *)header, 4)) {
+	if (region_allocate(region, (char *)entry - (char *)header, sizeof(__u32))) {
 		if (fix_problem(ctx, PR_1_EA_ALLOC_COLLISION, pctx))
 			goto clear_extattr;
 	}
-- 
2.55.0


  parent reply	other threads:[~2026-09-24 22:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24 22:23 [PATCH 0/8] e2fsprogs: fix extended attribute iteration loop bounds checking Eric Sandeen
2026-09-24 22:23 ` [PATCH 1/8] e2fsck: fix in-inode extended attribute checking Eric Sandeen
2026-09-24 22:23 ` Eric Sandeen [this message]
2026-09-24 22:23 ` [PATCH 3/8] e2fsck: fix ea loop in inc_ea_inode_refs Eric Sandeen
2026-09-24 22:23 ` [PATCH 4/8] libext2fs: fix ea loop in ext2fs_ext_attr_block_rehash Eric Sandeen
2026-09-24 22:23 ` [PATCH 5/8] libext2fs: fix ea loop in read_xattrs_from_buffer Eric Sandeen
2026-09-24 22:23 ` [PATCH 6/8] tune2fs: fix ea loop in update_xattr_entry_hashes Eric Sandeen
2026-09-24 22:23 ` [PATCH 7/8] resize2fs: " Eric Sandeen
2026-09-24 22:23 ` [PATCH 8/8] libext2fs: fix ea loop in ext2fs_xattr_inode_max_size Eric Sandeen

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=20260924222944.3683556-3-sandeen@redhat.com \
    --to=sandeen@redhat.com \
    --cc=agruenba@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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