From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>,
BAREBOX <barebox@lists.infradead.org>
Cc: "Claude Opus 4.6 (1M context)" <noreply@anthropic.com>
Subject: Re: [PATCH 1/5] fs: ext4: validate log2_block_size from superblock at mount
Date: Fri, 10 Apr 2026 13:33:42 +0200 [thread overview]
Message-ID: <54065682-b075-4e83-8598-6709328d74e2@pengutronix.de> (raw)
In-Reply-To: <20260402-fs-ext4-buffer-overflows-v1-1-b9f8a909fe58@pengutronix.de>
On 4/2/26 12:12 PM, Sascha Hauer wrote:
> The superblock's log2_block_size field is read from disk and used
> throughout the ext4 code without validation. EXT2_BLOCK_SIZE() computes
> 1 << (log2_block_size + 10), so a crafted value of 22 or larger causes
> undefined behavior from shifting an int by >= 32 bits.
>
> This leads to wrong allocation sizes for indirect block buffers and
> enables downstream buffer overflows in every function that reads
> block-sized data.
>
> Validate that log2_block_size does not exceed the maximum defined by
> EXT2_MAX_BLOCK_LOG_SIZE (65536 byte blocks) at mount time, rejecting
> the filesystem early if it does.
>
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Reviewed-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
This is analogous to Linux commit 62aeb94433fc ("ext2: Check block size
validity during mount"), which addressed a Syzbot report in 2023.
> ---
> fs/ext4/ext4_common.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/fs/ext4/ext4_common.c b/fs/ext4/ext4_common.c
> index a38593105f..094293a069 100644
> --- a/fs/ext4/ext4_common.c
> +++ b/fs/ext4/ext4_common.c
> @@ -514,6 +514,14 @@ int ext4fs_mount(struct ext_filesystem *fs)
> goto fail;
> }
>
> + if (le32_to_cpu(data->sblock.log2_block_size) >
> + EXT2_MAX_BLOCK_LOG_SIZE - EXT2_MIN_BLOCK_LOG_SIZE) {
> + dev_err(fs->dev, "invalid block size %u\n",> +
le32_to_cpu(data->sblock.log2_block_size));
> + ret = -EINVAL;
> + goto fail;
> + }
> +
> if (le32_to_cpu(data->sblock.revision_level) == 0) {
> fs->inodesz = 128;
> fs->gdsize = 32;
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2026-04-10 11:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 10:12 [PATCH 0/5] fs: ext4: protection against corrupted filesystems Sascha Hauer
2026-04-02 10:12 ` [PATCH 1/5] fs: ext4: validate log2_block_size from superblock at mount Sascha Hauer
2026-04-10 11:33 ` Ahmad Fatoum [this message]
2026-04-02 10:12 ` [PATCH 2/5] fs: ext4: reject superblocks with zero inodesz, gdsize or inodes_per_group Sascha Hauer
2026-04-10 11:51 ` Ahmad Fatoum
2026-04-02 10:12 ` [PATCH 3/5] fs: ext4: fix OOB read and infinite loop in ext_iterate() Sascha Hauer
2026-04-02 10:45 ` Sascha Hauer
2026-04-02 10:12 ` [PATCH 4/5] fs: ext4: reject dirents with too-small direntlen to prevent infinite loops Sascha Hauer
2026-04-02 10:12 ` [PATCH 5/5] fs: ext4: validate extent eh_entries against buffer capacity Sascha Hauer
2026-04-13 8:01 ` [PATCH 0/5] fs: ext4: protection against corrupted filesystems Sascha Hauer
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=54065682-b075-4e83-8598-6709328d74e2@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=noreply@anthropic.com \
--cc=s.hauer@pengutronix.de \
/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