public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukas Czerner <lczerner@redhat.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: "Ext4 Developers List" <linux-ext4@vger.kernel.org>,
	"Nils Bars" <nils.bars@rub.de>,
	"Moritz Schlögel" <moritz.schloegel@rub.de>,
	"Nico Schiller" <nico.schiller@rub.de>
Subject: Re: [PATCH 1/7] e2fsck: sanity check the journal inode number
Date: Tue, 7 Jun 2022 15:12:30 +0200	[thread overview]
Message-ID: <20220607131230.vwlqysdihghwwpyx@fedora> (raw)
In-Reply-To: <20220607042444.1798015-2-tytso@mit.edu>

On Tue, Jun 07, 2022 at 12:24:38AM -0400, Theodore Ts'o wrote:
> E2fsck replays the journal before sanity checking the full superblock.
> So it's possible that the journal inode number is not valid relative
> to the number of block groups.  So to avoid potentially an array
> bounds overrun, sanity check this before trying to find the journal
> inode.

Looks good.

Reviewed-by: Lukas Czerner <lczerner@redhat.com>

> 
> Reported-by: Nils Bars <nils.bars@rub.de>
> Reported-by: Moritz Schlögel <moritz.schloegel@rub.de>
> Reported-by: Nico Schiller <nico.schiller@rub.de>
> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
> ---
>  e2fsck/journal.c | 9 ++++++++-
>  1 file changed, 8 insertions(+), 1 deletion(-)
> 
> diff --git a/e2fsck/journal.c b/e2fsck/journal.c
> index 2e867234..12487e3d 100644
> --- a/e2fsck/journal.c
> +++ b/e2fsck/journal.c
> @@ -989,7 +989,14 @@ static errcode_t e2fsck_get_journal(e2fsck_t ctx, journal_t **ret_journal)
>  	journal->j_blocksize = ctx->fs->blocksize;
>  
>  	if (uuid_is_null(sb->s_journal_uuid)) {
> -		if (!sb->s_journal_inum) {
> +		/*
> +		 * The full set of superblock sanity checks haven't
> +		 * been performed yet, so we need to do some basic
> +		 * checks here to avoid potential array overruns.
> +		 */
> +		if (!sb->s_journal_inum ||
> +		    (sb->s_journal_inum >
> +		     (ctx->fs->group_desc_count * sb->s_inodes_per_group))) {
>  			retval = EXT2_ET_BAD_INODE_NUM;
>  			goto errout;
>  		}
> -- 
> 2.31.0
> 


  reply	other threads:[~2022-06-07 13:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07  4:24 [PATCH 0/7] Fix various bugs found via a fuzzing campaign Theodore Ts'o
2022-06-07  4:24 ` [PATCH 1/7] e2fsck: sanity check the journal inode number Theodore Ts'o
2022-06-07 13:12   ` Lukas Czerner [this message]
2022-06-07  4:24 ` [PATCH 2/7] e2fsck: fix potential out-of-bounds read in inc_ea_inode_refs() Theodore Ts'o
2022-06-07 13:30   ` Lukas Czerner
2022-06-07  4:24 ` [PATCH 3/7] libext2fs: add check for too-short directory blocks Theodore Ts'o
2022-06-07 13:31   ` Lukas Czerner
2022-06-07  4:24 ` [PATCH 4/7] e2fsck: check for xattr value size integer wraparound Theodore Ts'o
2022-06-07 13:33   ` Lukas Czerner
2022-06-07  4:24 ` [PATCH 5/7] e2fsck: avoid out-of-bounds write for very deep extent trees Theodore Ts'o
2022-06-07 13:53   ` Lukas Czerner
2022-06-07  4:24 ` [PATCH 6/7] libext2fs: check for cyclic loops in the extent tree Theodore Ts'o
2022-06-07 14:11   ` Lukas Czerner
2022-06-07  4:24 ` [PATCH 7/7] libext2fs: check for invalid blocks in ext2fs_punch_blocks() Theodore Ts'o
2022-06-07 14:22   ` Lukas Czerner

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=20220607131230.vwlqysdihghwwpyx@fedora \
    --to=lczerner@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=moritz.schloegel@rub.de \
    --cc=nico.schiller@rub.de \
    --cc=nils.bars@rub.de \
    --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