From: Eric Sandeen <sandeen@redhat.com>
To: linux-ext4@vger.kernel.org
Cc: tytso@mit.edu, sandeen@redhat.com, agruenba@redhat.com
Subject: [PATCH 8/8] libext2fs: fix ea loop in ext2fs_xattr_inode_max_size
Date: Thu, 24 Sep 2026 17:23:42 -0500 [thread overview]
Message-ID: <20260924222944.3683556-9-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().
Found by AISLE in partnership with Red Hat.
Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
lib/ext2fs/ext_attr.c | 17 ++++++++++++++---
1 file changed, 14 insertions(+), 3 deletions(-)
diff --git a/lib/ext2fs/ext_attr.c b/lib/ext2fs/ext_attr.c
index 6f6d2f4f..f2ac8911 100644
--- a/lib/ext2fs/ext_attr.c
+++ b/lib/ext2fs/ext_attr.c
@@ -1211,8 +1211,8 @@ errcode_t ext2fs_xattr_inode_max_size(ext2_filsys fs, ext2_ino_t ino,
struct ext2_ext_attr_entry *entry;
struct ext2_inode_large *inode;
__u32 ea_inode_magic;
- unsigned int minoff;
- char *start;
+ unsigned int minoff, remain;
+ char *start, *end;
size_t i;
errcode_t err;
@@ -1241,14 +1241,25 @@ errcode_t ext2fs_xattr_inode_max_size(ext2_filsys fs, ext2_ino_t ino,
inode->i_extra_isize, sizeof(__u32));
if (ea_inode_magic == EXT2_EXT_ATTR_MAGIC) {
/* has xattrs. calculate the size */
- start= ((char *) inode) + EXT2_GOOD_OLD_INODE_SIZE +
+ start = ((char *) inode) + EXT2_GOOD_OLD_INODE_SIZE +
inode->i_extra_isize + sizeof(__u32);
+ end = (char *)inode + EXT2_INODE_SIZE(fs->super);
+ /* take finish entry 0UL into account */
+ remain = end - (char *)start - sizeof(__u32);
entry = (struct ext2_ext_attr_entry *) start;
while (!EXT2_EXT_IS_LAST_ENTRY(entry)) {
+ /* end->e_name_len is within the first four bytes */
+ if (EXT2_EXT_ATTR_LEN(entry->e_name_len) > remain)
+ return EXT2_ET_INLINE_DATA_NO_SPACE;
+ remain -= EXT2_EXT_ATTR_LEN(entry->e_name_len);
+
if (!entry->e_value_inum && entry->e_value_size) {
unsigned int offs = entry->e_value_offs;
if (offs < minoff)
minoff = offs;
+ if (EXT2_EXT_ATTR_SIZE(entry->e_value_size) > remain)
+ return EXT2_ET_INLINE_DATA_NO_SPACE;
+ remain -= EXT2_EXT_ATTR_SIZE(entry->e_value_size);
}
entry = EXT2_EXT_ATTR_NEXT(entry);
}
--
2.55.0
prev 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 ` [PATCH 2/8] e2fsck: fix extended attribute block checking Eric Sandeen
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 ` Eric Sandeen [this message]
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-9-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