From: Eric Sandeen <sandeen@redhat.com>
To: Haogang Chen <haogangchen@gmail.com>
Cc: Theodore Tso <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
Yongqiang Yang <xiaoqiangnk@gmail.com>
Subject: Re: [PATCH] FS: ext4: fix integer overflow in alloc_flex_gd()
Date: Mon, 20 Feb 2012 17:47:44 -0600 [thread overview]
Message-ID: <4F42DBA0.4090502@redhat.com> (raw)
In-Reply-To: <1329777684-18396-1-git-send-email-haogangchen@gmail.com>
On 2/20/12 4:41 PM, Haogang Chen wrote:
> In alloc_flex_gd(), when flexbg_size is large, kmalloc size would
> overflow and flex_gd->groups would point to a buffer smaller than
> expected, causing OOB accesses when it is used.
>
> Note that in ext4_resize_fs(), flexbg_size is calculated using
> sbi->s_log_groups_per_flex, which is read from the disk and only bounded
> to [1, 31]. The patch returns NULL for too large flexbg_size
Hm this raises a few questions I think.
On the one hand, making sure the kmalloc arg doesn't overflow here is
certainly a good thing and probably the right thing to do in the short term.
So I guess:
Reviewed-by: Eric Sandeen <sandeen@redhat.com>
for that, to close the hole.
But the types are a mess; alloc_flex_gd() takes an unsigned long;
it's passed an int, and assigns to flex_gd->count, an ext4_group_t
(which is an unsigned int). They should probably all be ext4_group_t
for consistency.
But that's not the worst of it...
Doesn't this also mean that a valid s_log_groups_per_flex (i.e. 31)
will fail in this resize code? That would be an unexpected outcome.
2^31 groups per flex is a little crazy, but still technically valid
according to the limits in the code.
So really, trying to allocate an array of all possible groups-per-flex
in the resize code is probably a really bad idea to start with, and the
resize code has got serious problems if kmalloc(UINT_MAX-1) is expected
to work...
-Eric
> Signed-off-by: Haogang Chen <haogangchen@gmail.com>
> ---
> fs/ext4/resize.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/fs/ext4/resize.c b/fs/ext4/resize.c
> index f9d948f..8601f4b 100644
> --- a/fs/ext4/resize.c
> +++ b/fs/ext4/resize.c
> @@ -161,6 +161,8 @@ static struct ext4_new_flex_group_data *alloc_flex_gd(unsigned long flexbg_size)
> if (flex_gd == NULL)
> goto out3;
>
> + if (flexbg_size >= UINT_MAX / sizeof(struct ext4_new_flex_group_data))
> + goto out2;
> flex_gd->count = flexbg_size;
>
> flex_gd->groups = kmalloc(sizeof(struct ext4_new_group_data) *
next prev parent reply other threads:[~2012-02-20 23:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 22:41 [PATCH] FS: ext4: fix integer overflow in alloc_flex_gd() Haogang Chen
2012-02-20 23:47 ` Eric Sandeen [this message]
2012-02-21 13:55 ` Xi Wang
2012-02-21 16:36 ` Eric Sandeen
2012-02-21 17:19 ` Andreas Dilger
2012-05-28 18:24 ` Ted Ts'o
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=4F42DBA0.4090502@redhat.com \
--to=sandeen@redhat.com \
--cc=adilger.kernel@dilger.ca \
--cc=haogangchen@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=xiaoqiangnk@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).