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 0/2] tools/nolibc: check for overflow in malloc()
Date: Sat, 26 Sep 2026 08:43:30 -0500 [thread overview]
Message-ID: <20260926134332.58184-1-danishkhateeb03@gmail.com> (raw)
malloc() does not check its size arithmetic for overflow, so
malloc(SIZE_MAX), calloc(SIZE_MAX, 1) and realloc(ptr, SIZE_MAX) return
a single page instead of NULL, and slightly smaller sizes fail with
EINVAL instead of ENOMEM.
Patch 1 fixes it. Patch 2 adds nolibc-test cases for huge sizes, which
would have caught it.
Tested on top of nolibc/for-next 0e1c44b472e1, on x86_64 (GCC and
clang) and i386, and on arm, arm64 and sparc64 under qemu-user:
- nolibc-test, all tests: no failures with the series. The only
difference from before is the three new tests, which pass. They also
pass against glibc (make libc-test), which builds without warnings.
- Without patch 1, all three new tests fail on every build:
malloc(SIZE_MAX) and calloc(SIZE_MAX, 1) return a pointer, and
malloc(SIZE_MAX - 4096) fails with EINVAL.
- On x86_64, a separate program shows realloc(ptr, SIZE_MAX) returning
a pointer before patch 1 and NULL with ENOMEM after it.
Danish Khateeb (2):
tools/nolibc: check for overflow in malloc()
selftests/nolibc: test malloc() and calloc() with huge sizes
tools/include/nolibc/stdlib.h | 12 +++++++++---
tools/testing/selftests/nolibc/nolibc-test.c | 11 +++++++++++
2 files changed, 20 insertions(+), 3 deletions(-)
base-commit: 0e1c44b472e1ec21efdad1df21b10e5c568b65b5
--
2.55.0
next reply other threads:[~2026-09-26 13:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 13:43 Danish Khateeb [this message]
2026-09-26 13:43 ` [PATCH 1/2] " Danish Khateeb
2026-09-26 14:17 ` Thomas Weißschuh
2026-09-26 13:43 ` [PATCH 2/2] selftests/nolibc: test malloc() and calloc() with huge sizes 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=20260926134332.58184-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®