public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] elf: fix NT_FILE integer overflow
Date: Sat, 13 Jan 2018 12:14:59 +0300	[thread overview]
Message-ID: <20180113091458.GA2533@avx2> (raw)
In-Reply-To: <20180112145208.b054caf00c6fa666cc1a1c9c@linux-foundation.org>

On Fri, Jan 12, 2018 at 02:52:08PM -0800, Andrew Morton wrote:
> On Fri, 12 Jan 2018 23:34:27 +0300 Alexey Dobriyan <adobriyan@gmail.com> wrote:
> 
> > If vm.max_map_count bumped above 2^26 (67+ mil) and system has enough
> > RAM to allocate all the VMAs (~12.8 GB on Fedora 27 with 200-byte VMAs),
> > then it should be possible to overflow 32-bit "size", pass paranoia check,
> > allocate very little vmalloc space and oops while writing into vmalloc
> > guard page...
> > 
> > But I didn't test this, only coredump of regular process.
> > 
> > ...
> >
> > --- a/fs/binfmt_elf.c
> > +++ b/fs/binfmt_elf.c
> > @@ -1599,6 +1599,8 @@ static int fill_files_note(struct memelfnote *note)
> >  
> >  	/* *Estimated* file count and total data size needed */
> >  	count = current->mm->map_count;
> > +	if (count > UINT_MAX / 64)
> > +		return -EINVAL;
> >  	size = count * 64;
> >  
> >  	names_ofs = (2 + 3 * count) * sizeof(data[0]);
> 
> Why not make `size' a ulong (or size_t)?  That seems to be the
> appropriate type and the code will then immediately barf over the
> MAX_FILE_NOTE_SIZE comparison anyway.

You can do it, but MAX_FILE_NOTE_SIZE is only 4 MB, and 32-bit code is
smaller than 64-bit code.

      reply	other threads:[~2018-01-13  9:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-12 20:34 [PATCH] elf: fix NT_FILE integer overflow Alexey Dobriyan
2018-01-12 22:52 ` Andrew Morton
2018-01-13  9:14   ` Alexey Dobriyan [this message]

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=20180113091458.GA2533@avx2 \
    --to=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /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