From: "Marvin Häuser" <mhaeuser@posteo.de>
To: Pedro Falcato <pedro.falcato@gmail.com>
Cc: Savva Mitrofanov <savvamtr@gmail.com>,
devel@edk2.groups.io, Vitaly Cheptsov <vit9696@protonmail.com>
Subject: Re: [edk2-platforms][PATCH v3 05/11] Ext4Pkg: Fix shift out of bounds in Ext4OpenSuperblock
Date: Fri, 27 Jan 2023 14:24:15 +0000 [thread overview]
Message-ID: <E100B286-3DDC-4BA6-A807-D725D7B15DF4@posteo.de> (raw)
In-Reply-To: <CAKbZUD2XM3Sq_X_Z2adVsQN=Ag7m1pNa_HN1v7Jtfr3KnZFtiA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3174 bytes --]
Reviewed-by: Marvin Häuser <mhaeuser@posteo.de>
> On 27. Jan 2023, at 15:22, Pedro Falcato <pedro.falcato@gmail.com> wrote:
>
> On Fri, Jan 27, 2023 at 9:29 AM Savva Mitrofanov <savvamtr@gmail.com <mailto:savvamtr@gmail.com>> wrote:
>>
>> Missing check for wrong s_log_block_size exponent leads to shift out of
>> bounds. Limit block size to 2 MiB
>>
>> Cc: Marvin Häuser <mhaeuser@posteo.de>
>> Cc: Pedro Falcato <pedro.falcato@gmail.com>
>> Cc: Vitaly Cheptsov <vit9696@protonmail.com>
>> Fixes: d9ceedca6c8f ("Ext4Pkg: Add Ext4Dxe driver.")
>> Signed-off-by: Savva Mitrofanov <savvamtr@gmail.com>
>> ---
>> Features/Ext4Pkg/Ext4Dxe/Ext4Dxe.h | 14 ++++++++++++++
>> Features/Ext4Pkg/Ext4Dxe/Superblock.c | 5 +++++
>> 2 files changed, 19 insertions(+)
>>
>> diff --git a/Features/Ext4Pkg/Ext4Dxe/Ext4Dxe.h b/Features/Ext4Pkg/Ext4Dxe/Ext4Dxe.h
>> index 2e489ce4dd86..a23323319a59 100644
>> --- a/Features/Ext4Pkg/Ext4Dxe/Ext4Dxe.h
>> +++ b/Features/Ext4Pkg/Ext4Dxe/Ext4Dxe.h
>> @@ -40,6 +40,20 @@
>> #define EXT4_EFI_PATH_MAX 4096
>> #define EXT4_DRIVER_VERSION 0x0000
>>
>> +//
>> +// The EXT4 Specification doesn't strictly limit block size and this value could be up to 2^31,
>> +// but in practice it is limited by PAGE_SIZE due to performance significant impact.
>> +// Many EXT4 implementations have size of block limited to PAGE_SIZE. In many cases it's limited
>> +// to 4096, which is a commonly supported page size on most MMU-capable hardware, and up to 65536.
>> +// So, to take a balance between compatibility and security measures, it is decided to use the
>> +// value of 2MiB as the limit, which is equal to page size on new hardware.
> Nit: s/page size/large page size/
> I can change this for you when pushing, no need for a v4 on this one.
>> +// As for supporting big block sizes, EXT4 has a RO_COMPAT_FEATURE called BIGALLOC, which changes
>> +// EXT4 to use clustered allocation, so that each bit in the ext4 block allocation bitmap addresses
>> +// a power of two number of blocks. So it would be wiser to implement and use this feature
>> +// if there is such a need instead of big block size.
>> +//
>> +#define EXT4_LOG_BLOCK_SIZE_MAX 11
>> +
>> /**
>> Opens an ext4 partition and installs the Simple File System protocol.
>>
>> diff --git a/Features/Ext4Pkg/Ext4Dxe/Superblock.c b/Features/Ext4Pkg/Ext4Dxe/Superblock.c
>> index be3527e4d618..3f56de93c105 100644
>> --- a/Features/Ext4Pkg/Ext4Dxe/Superblock.c
>> +++ b/Features/Ext4Pkg/Ext4Dxe/Superblock.c
>> @@ -248,6 +248,11 @@ Ext4OpenSuperblock (
>> return EFI_VOLUME_CORRUPTED;
>> }
>>
>> + if (Sb->s_log_block_size > EXT4_LOG_BLOCK_SIZE_MAX) {
>> + DEBUG ((DEBUG_ERROR, "[ext4] SuperBlock s_log_block_size %lu is too big\n", Sb->s_log_block_size));
>> + return EFI_UNSUPPORTED;
>> + }
>> +
>> Partition->BlockSize = (UINT32)LShiftU64 (1024, Sb->s_log_block_size);
>>
>> // The size of a block group can also be calculated as 8 * Partition->BlockSize
>> --
>> 2.39.0
>>
>
> Reviewed-by: Pedro Falcato <pedro.falcato@gmail.com <mailto:pedro.falcato@gmail.com>>
>
> --
> Pedro
[-- Attachment #2: Type: text/html, Size: 10383 bytes --]
next prev parent reply other threads:[~2023-01-27 14:24 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 9:29 [edk2-platforms][PATCH v3 00/11] Ext4Pkg: Code correctness and security improvements Savva Mitrofanov
2023-01-27 9:29 ` [edk2-platforms][PATCH v3 01/11] Ext4Pkg: Fix memory leak in Ext4RetrieveDirent Savva Mitrofanov
2023-01-27 14:12 ` Pedro Falcato
2023-01-27 14:16 ` Marvin Häuser
2023-01-27 9:29 ` [edk2-platforms][PATCH v3 02/11] Ext4Pkg: Fix incorrect checksum metadata feature check Savva Mitrofanov
2023-01-27 10:02 ` Marvin Häuser
2023-01-27 14:29 ` Pedro Falcato
2023-01-30 8:38 ` Marvin Häuser
2023-01-30 8:42 ` Savva Mitrofanov
2023-01-27 9:29 ` [edk2-platforms][PATCH v3 03/11] Ext4Pkg: Fix division by zero by adding check for s_inodes_per_group Savva Mitrofanov
2023-01-27 14:13 ` Pedro Falcato
2023-01-27 14:16 ` Marvin Häuser
2023-01-27 9:29 ` [edk2-platforms][PATCH v3 04/11] Ext4Pkg: Add inode number validity check Savva Mitrofanov
2023-01-27 14:19 ` Pedro Falcato
2023-02-02 10:15 ` Savva Mitrofanov
2023-01-27 9:29 ` [edk2-platforms][PATCH v3 05/11] Ext4Pkg: Fix shift out of bounds in Ext4OpenSuperblock Savva Mitrofanov
2023-01-27 14:22 ` Pedro Falcato
2023-01-27 14:24 ` Marvin Häuser [this message]
2023-01-27 16:14 ` Savva Mitrofanov
2023-01-27 9:29 ` [edk2-platforms][PATCH v3 06/11] Ext4Pkg: Corrects integer overflow check logic in DiskUtil Savva Mitrofanov
2023-01-27 14:24 ` Pedro Falcato
2023-01-27 16:10 ` Savva Mitrofanov
2023-01-27 16:21 ` Pedro Falcato
2023-01-27 9:29 ` [edk2-platforms][PATCH v3 07/11] Ext4Pkg: Check that source file is directory in Ext4OpenInternal Savva Mitrofanov
2023-01-27 14:26 ` Pedro Falcato
2023-01-27 14:33 ` Marvin Häuser
2023-01-27 9:29 ` [edk2-platforms][PATCH v3 08/11] Ext4Pkg: Check VolumeName allocation correctness in Ext4GetVolumeName Savva Mitrofanov
2023-01-27 14:27 ` [edk2-devel] " Pedro Falcato
2023-01-27 14:34 ` Marvin Häuser
2023-01-27 9:29 ` [edk2-platforms][PATCH v3 09/11] Ext4Pkg: Add missing exit Status in Ext4OpenDirent Savva Mitrofanov
2023-01-27 14:28 ` Pedro Falcato
2023-01-27 14:34 ` Marvin Häuser
2023-01-27 9:29 ` [edk2-platforms][PATCH v3 10/11] Ext4Pkg: Fixes build on MSVC Savva Mitrofanov
2023-01-27 14:33 ` Pedro Falcato
2023-01-27 14:36 ` Marvin Häuser
2023-01-30 8:35 ` Marvin Häuser
2023-01-27 9:29 ` [edk2-platforms][PATCH v3 11/11] Ext4Pkg: Filter out directory entry names containing \0 as invalid Savva Mitrofanov
2023-01-27 10:04 ` Marvin Häuser
2023-01-27 14:09 ` Pedro Falcato
2023-01-27 14:14 ` Marvin Häuser
2023-01-30 8:48 ` Marvin Häuser
2023-01-30 8:19 ` Savva Mitrofanov
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-list 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=E100B286-3DDC-4BA6-A807-D725D7B15DF4@posteo.de \
--to=devel@edk2.groups.io \
/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