mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* [PATCH] f2fs: bound i_inline_xattr_size for non-inline-xattr inodes
@ 2026-06-12  4:00 Bryam Vargas via B4 Relay
  2026-06-16  2:50 ` [f2fs-dev] " patchwork-bot+f2fs
  2026-06-16  8:55 ` Chao Yu
  0 siblings, 2 replies; 3+ messages in thread
From: Bryam Vargas via B4 Relay @ 2026-06-12  4:00 UTC (permalink / raw)
  To: Jaegeuk Kim, Chao Yu; +Cc: linux-f2fs-devel, linux-kernel

From: Bryam Vargas <hexlabsecurity@proton.me>

When the flexible_inline_xattr feature is enabled, do_read_inode() loads
the on-disk i_inline_xattr_size unconditionally:

	if (f2fs_sb_has_flexible_inline_xattr(sbi))
		fi->i_inline_xattr_size = le16_to_cpu(ri->i_inline_xattr_size);

but sanity_check_inode() only range-checks it when the inode also has the
FI_INLINE_XATTR flag set.  An inode that carries an inline dentry or inline
data but not FI_INLINE_XATTR -- the normal layout for an inline
directory -- therefore keeps a fully attacker-controlled
i_inline_xattr_size from a crafted image.

get_inline_xattr_addrs() returns that value with no flag gating, so it
feeds the inode geometry:

	MAX_INLINE_DATA()  = 4 * (CUR_ADDRS_PER_INODE - i_inline_xattr_size - 1)
	NR_INLINE_DENTRY() = MAX_INLINE_DATA() * BITS_PER_BYTE / (...)
	addrs_per_page()   = CUR_ADDRS_PER_INODE - i_inline_xattr_size

A large i_inline_xattr_size drives MAX_INLINE_DATA() and NR_INLINE_DENTRY()
negative, so make_dentry_ptr_inline() sets d->max (int) to a negative
value.  The inline directory walk then compares an unsigned long bit_pos
against that negative d->max, which is promoted to a huge unsigned bound,
and reads far past the inline area:

	while (bit_pos < d->max)		/* fs/f2fs/dir.c */
		... test_bit_le(bit_pos, d->bitmap) / d->dentry[bit_pos] ...

Mounting a crafted image and reading such a directory triggers an
out-of-bounds read in f2fs_fill_dentries(); the same underflow also
corrupts ADDRS_PER_INODE for regular files.

Validate i_inline_xattr_size against MAX_INLINE_XATTR_SIZE whenever the
flexible_inline_xattr feature is enabled -- i.e. whenever the value is
loaded from disk and consumed -- and keep the lower MIN_INLINE_XATTR_SIZE
bound gated on inodes that actually carry an inline xattr, so legitimate
inodes with i_inline_xattr_size == 0 are still accepted.

Fixes: 6afc662e68b5 ("f2fs: support flexible inline xattr size")
Cc: stable@vger.kernel.org
Signed-off-by: Bryam Vargas <hexlabsecurity@proton.me>
---
 fs/f2fs/inode.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/fs/f2fs/inode.c b/fs/f2fs/inode.c
index c6dcda447882..5c0f62190875 100644
--- a/fs/f2fs/inode.c
+++ b/fs/f2fs/inode.c
@@ -324,9 +324,9 @@ static bool sanity_check_inode(struct inode *inode, struct folio *node_folio)
 	}
 
 	if (f2fs_sb_has_flexible_inline_xattr(sbi) &&
-		f2fs_has_inline_xattr(inode) &&
-		(fi->i_inline_xattr_size < MIN_INLINE_XATTR_SIZE ||
-		fi->i_inline_xattr_size > MAX_INLINE_XATTR_SIZE)) {
+		(fi->i_inline_xattr_size > MAX_INLINE_XATTR_SIZE ||
+		(f2fs_has_inline_xattr(inode) &&
+		fi->i_inline_xattr_size < MIN_INLINE_XATTR_SIZE))) {
 		f2fs_warn(sbi, "%s: inode (ino=%llx) has corrupted i_inline_xattr_size: %d, min: %zu, max: %lu",
 			  __func__, inode->i_ino, fi->i_inline_xattr_size,
 			  MIN_INLINE_XATTR_SIZE, MAX_INLINE_XATTR_SIZE);

---
base-commit: 8e65320d91cdc3b241d4b94855c88459b91abf66
change-id: 20260611-b4-disp-155e8807-81fd7e4d00ac

Best regards,
-- 
Bryam Vargas <hexlabsecurity@proton.me>



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [f2fs-dev] [PATCH] f2fs: bound i_inline_xattr_size for non-inline-xattr inodes
  2026-06-12  4:00 [PATCH] f2fs: bound i_inline_xattr_size for non-inline-xattr inodes Bryam Vargas via B4 Relay
@ 2026-06-16  2:50 ` patchwork-bot+f2fs
  2026-06-16  8:55 ` Chao Yu
  1 sibling, 0 replies; 3+ messages in thread
From: patchwork-bot+f2fs @ 2026-06-16  2:50 UTC (permalink / raw)
  To: Bryam Vargas
  Cc: jaegeuk, chao, devnull+hexlabsecurity.proton.me, linux-kernel,
	linux-f2fs-devel

Hello:

This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:

On Thu, 11 Jun 2026 23:00:36 -0500 you wrote:
> From: Bryam Vargas <hexlabsecurity@proton.me>
> 
> When the flexible_inline_xattr feature is enabled, do_read_inode() loads
> the on-disk i_inline_xattr_size unconditionally:
> 
> 	if (f2fs_sb_has_flexible_inline_xattr(sbi))
> 		fi->i_inline_xattr_size = le16_to_cpu(ri->i_inline_xattr_size);
> 
> [...]

Here is the summary with links:
  - [f2fs-dev] f2fs: bound i_inline_xattr_size for non-inline-xattr inodes
    https://git.kernel.org/jaegeuk/f2fs/c/ca29fc0196bd

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] f2fs: bound i_inline_xattr_size for non-inline-xattr inodes
  2026-06-12  4:00 [PATCH] f2fs: bound i_inline_xattr_size for non-inline-xattr inodes Bryam Vargas via B4 Relay
  2026-06-16  2:50 ` [f2fs-dev] " patchwork-bot+f2fs
@ 2026-06-16  8:55 ` Chao Yu
  1 sibling, 0 replies; 3+ messages in thread
From: Chao Yu @ 2026-06-16  8:55 UTC (permalink / raw)
  To: hexlabsecurity, Jaegeuk Kim; +Cc: chao, linux-f2fs-devel, linux-kernel

On 6/12/26 12:00, Bryam Vargas via B4 Relay wrote:
> From: Bryam Vargas <hexlabsecurity@proton.me>
> 
> When the flexible_inline_xattr feature is enabled, do_read_inode() loads
> the on-disk i_inline_xattr_size unconditionally:
> 
> 	if (f2fs_sb_has_flexible_inline_xattr(sbi))
> 		fi->i_inline_xattr_size = le16_to_cpu(ri->i_inline_xattr_size);
> 
> but sanity_check_inode() only range-checks it when the inode also has the
> FI_INLINE_XATTR flag set.  An inode that carries an inline dentry or inline
> data but not FI_INLINE_XATTR -- the normal layout for an inline
> directory -- therefore keeps a fully attacker-controlled
> i_inline_xattr_size from a crafted image.
> 
> get_inline_xattr_addrs() returns that value with no flag gating, so it
> feeds the inode geometry:
> 
> 	MAX_INLINE_DATA()  = 4 * (CUR_ADDRS_PER_INODE - i_inline_xattr_size - 1)
> 	NR_INLINE_DENTRY() = MAX_INLINE_DATA() * BITS_PER_BYTE / (...)
> 	addrs_per_page()   = CUR_ADDRS_PER_INODE - i_inline_xattr_size
> 
> A large i_inline_xattr_size drives MAX_INLINE_DATA() and NR_INLINE_DENTRY()
> negative, so make_dentry_ptr_inline() sets d->max (int) to a negative
> value.  The inline directory walk then compares an unsigned long bit_pos
> against that negative d->max, which is promoted to a huge unsigned bound,
> and reads far past the inline area:
> 
> 	while (bit_pos < d->max)		/* fs/f2fs/dir.c */
> 		... test_bit_le(bit_pos, d->bitmap) / d->dentry[bit_pos] ...
> 
> Mounting a crafted image and reading such a directory triggers an
> out-of-bounds read in f2fs_fill_dentries(); the same underflow also
> corrupts ADDRS_PER_INODE for regular files.
> 
> Validate i_inline_xattr_size against MAX_INLINE_XATTR_SIZE whenever the
> flexible_inline_xattr feature is enabled -- i.e. whenever the value is
> loaded from disk and consumed -- and keep the lower MIN_INLINE_XATTR_SIZE
> bound gated on inodes that actually carry an inline xattr, so legitimate
> inodes with i_inline_xattr_size == 0 are still accepted.
> 
> Fixes: 6afc662e68b5 ("f2fs: support flexible inline xattr size")
> Cc: stable@vger.kernel.org
> Signed-off-by: Bryam Vargas <hexlabsecurity@proton.me>

Reviewed-by: Chao Yu <chao@kernel.org>

Thanks,

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2026-06-16  8:55 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-06-12  4:00 [PATCH] f2fs: bound i_inline_xattr_size for non-inline-xattr inodes Bryam Vargas via B4 Relay
2026-06-16  2:50 ` [f2fs-dev] " patchwork-bot+f2fs
2026-06-16  8:55 ` Chao Yu

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®