From: Danish Khateeb <danishkhateeb03@gmail.com>
To: "Willy Tarreau" <w@1wt.eu>, "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Danish Khateeb <danishkhateeb03@gmail.com>
Subject: [PATCH v2 0/2] tools/nolibc: check for overflow in malloc()
Date: Sat, 26 Sep 2026 10:24:12 -0500 [thread overview]
Message-ID: <20260926152414.251214-1-danishkhateeb03@gmail.com> (raw)
malloc() does not check the addition of its header size for overflow,
so malloc(SIZE_MAX), calloc(SIZE_MAX, 1) and realloc(ptr, SIZE_MAX)
return a single page instead of NULL.
As suggested by Thomas, patch 1 drops the rounding to 4096 bytes, and
patch 2 adds the overflow check on top.
Tested on x86_64 (GCC and clang), i386, and on arm, arm64 and sparc64
under qemu-user:
- nolibc-test: no failures, with patch 1 alone and with the series.
- A separate program: malloc(), calloc() and realloc() with sizes close
to SIZE_MAX fail with ENOMEM, and free() still unmaps every page.
Changes in v2:
- Drop the rounding in a separate patch, instead of checking it for
overflow (Thomas)
- Drop the test patch (Thomas)
- Link to v1: https://lore.kernel.org/r/20260926134332.58184-1-danishkhateeb03@gmail.com
Danish Khateeb (2):
tools/nolibc: stop rounding malloc() sizes up to 4096 bytes
tools/nolibc: check for overflow in malloc()
tools/include/nolibc/stdlib.h | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
base-commit: 0e1c44b472e1ec21efdad1df21b10e5c568b65b5
--
2.55.0
next reply other threads:[~2026-09-26 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 15:24 Danish Khateeb [this message]
2026-09-26 15:24 ` [PATCH v2 1/2] tools/nolibc: stop rounding malloc() sizes up to 4096 bytes Danish Khateeb
2026-09-26 15:50 ` Thomas Weißschuh
2026-09-26 17:14 ` Willy Tarreau
2026-09-26 15:24 ` [PATCH v2 2/2] tools/nolibc: check for overflow in malloc() Danish Khateeb
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=20260926152414.251214-1-danishkhateeb03@gmail.com \
--to=danishkhateeb03@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=shuah@kernel.org \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®