From: Will Newton <will.newton@linaro.org>
Date: Fri, 16 Aug 2013 10:59:37 +0000 (+0100)
Subject: malloc: Check for integer overflow in valloc.
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=42b872e43db7c71cd40357724f1542252eb0c708;p=thirdparty%2Fglibc.git

malloc: Check for integer overflow in valloc.

A large bytes parameter to valloc could cause an integer overflow
and corrupt allocator internals. Check the overflow does not occur
before continuing with the allocation.

ChangeLog:

2013-09-11  Will Newton  <will.newton@linaro.org>

	[BZ #15856]
	* malloc/malloc.c (__libc_valloc): Check the value of bytes
	does not overflow.

(cherry picked from commit 6a6a386a3040726053a5fb8582ff26dc85d84741)
---

diff --git a/malloc/malloc.c b/malloc/malloc.c
index bcc08c45f7b..31e2dfad91e 100644
--- a/malloc/malloc.c
+++ b/malloc/malloc.c
@@ -3046,6 +3046,13 @@ __libc_valloc(size_t bytes)
 
   size_t pagesz = GLRO(dl_pagesize);
 
+  /* Check for overflow.  */
+  if (bytes > SIZE_MAX - pagesz - MINSIZE)
+    {
+      __set_errno (ENOMEM);
+      return 0;
+    }
+
   void *(*hook) (size_t, size_t, const void *) =
     force_reg (__memalign_hook);
   if (__builtin_expect (hook != NULL, 0))