From: Josh Law <objecting@objecting.org>
To: akpm@linux-foundation.org, pmladek@suse.com, rostedt@goodmis.org
Cc: andriy.shevchenko@linux.intel.com, linux@rasmusvillemoes.dk,
senozhatsky@chromium.org, linux-kernel@vger.kernel.org,
Josh Law <objecting@objecting.org>
Subject: [PATCH v2 0/2] lib/vsprintf: pointer handling fixes for bstr_printf() and vbin_printf()
Date: Mon, 30 Mar 2026 19:34:38 +0000 [thread overview]
Message-ID: <20260330193440.74268-1-objecting@objecting.org> (raw)
These patches address multiple bugs in vsprintf pointer handling
Patch one: Regards argument pointer advancement in bstr_printf(),
when the buffer is full..
Patch two: Fixes a OOB write in vbin_printf() when size is 0
Josh Law (2):
lib/vsprintf: always advance args in bstr_printf() pointer path
lib/vsprintf: fix OOB write in vbin_printf() when size is zero
lib/vsprintf.c | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
Changes since V1:
Dropped 2 patches, probably not needed.
For patch 2: Instead of using else if (end > (char *)bin_buf),
instead guard size with else if (size) /* do nothing if size is zero */
(suggested by steven Rostedt)
--
2.34.1
next reply other threads:[~2026-03-30 19:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 19:34 Josh Law [this message]
2026-03-30 19:34 ` [PATCH v2 1/2] lib/vsprintf: always advance args in bstr_printf() pointer path Josh Law
2026-03-31 7:26 ` Krzysztof Kozlowski
2026-03-31 14:47 ` Steven Rostedt
2026-04-02 3:47 ` Kuan-Wei Chiu
2026-04-02 8:03 ` Josh Law
2026-04-02 13:34 ` Steven Rostedt
2026-03-30 19:34 ` [PATCH v2 2/2] lib/vsprintf: fix OOB write in vbin_printf() when size is zero Josh Law
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=20260330193440.74268-1-objecting@objecting.org \
--to=objecting@objecting.org \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.