From: Peter Seiderer <ps.report@gmx.net>
To: Marc Buerg <buermarc@googlemail.com>
Cc: Kees Cook <kees@kernel.org>,
Joel Granados <joel.granados@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Octavian Purdila <opurdila@ixiacom.com>,
WANG Cong <amwang@redhat.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Elias Oezcan <elias.rw2@gmail.com>
Subject: Re: [PATCH v2] sysctl: fix check against uninitialized variable in proc_do_large_bitmap
Date: Thu, 19 Mar 2026 19:58:41 +0100 [thread overview]
Message-ID: <20260319195841.227edf09@pc-1> (raw)
In-Reply-To: <20260317-fix-uninitialized-variable-in-proc_do_large_bitmap-v2-1-6dfb1aefa287@googlemail.com>
Hello Marc,
thanks for new patch iteration, some minor comments below...
On Tue, 17 Mar 2026 22:39:32 +0100, Marc Buerg <buermarc@googlemail.com> wrote:
> proc_do_large_bitmap() does not initialize variable c, which is expected
> to be set to a trailing character by proc_get_long().
>
> However, proc_get_long() only sets c when the input buffer contains a
> trailing character after the parsed value.
>
> If c is not initialized it may happen to contain a '-'. If this is the
> case proc_do_large_bitmap() expects to be able to parse a second part of
> the input buffer. If there is no second part an unjustified -EINVAL will
> be returned.
>
> Add check that left is non-zero before checking c, as proc_get_long()
> ensures that the passed left is non-zero, if a trailing character
> exists.
>
> ---
All below this '---' comment marker will be dropped when applied
(specially the 'Fixes:' and 'Signed-off-by:' tags)...
> Fixes: 9f977fb7ae9d ("sysctl: add proc_do_large_bitmap")
> Signed-off-by: Marc Buerg <buermarc@googlemail.com>
> ---
> Changes in v2:
> - Drop initialization of c to 0
> - Include checking that left is non-zero before checking against c
> - Link to v1: https://lore.kernel.org/r/20260312-fix-uninitialized-variable-in-proc_do_large_bitmap-v1-1-35ad2dddaf21@googlemail.com
I personally found some of the commit message text from v1 very
nice/helpful, specially the part about the writing to
/proc/sys/net/ipv4/ip_local_reserved_ports to trigger/observe the bug and
the maybe condition on CONFIG_INIT_STACK_NONE=y...
Besides that you can add my
Reviewed-by: Peter Seiderer <ps.report@gmx.net>
Regards,
Peter
> ---
> kernel/sysctl.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/sysctl.c b/kernel/sysctl.c
> index 9d3a666ffde1..dd337a63da41 100644
> --- a/kernel/sysctl.c
> +++ b/kernel/sysctl.c
> @@ -1171,7 +1171,7 @@ int proc_do_large_bitmap(const struct ctl_table *table, int dir,
> left--;
> }
>
> - if (c == '-') {
> + if (left && c == '-') {
> err = proc_get_long(&p, &left, &val_b,
> &neg, tr_b, sizeof(tr_b),
> &c);
>
> ---
> base-commit: 80234b5ab240f52fa45d201e899e207b9265ef91
> change-id: 20260312-fix-uninitialized-variable-in-proc_do_large_bitmap-30c6ef4ac1c5
>
> Best regards,
next prev parent reply other threads:[~2026-03-19 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 21:39 [PATCH v2] sysctl: fix check against uninitialized variable in proc_do_large_bitmap Marc Buerg
2026-03-19 18:58 ` Peter Seiderer [this message]
2026-03-19 22:48 ` buermarc
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=20260319195841.227edf09@pc-1 \
--to=ps.report@gmx.net \
--cc=amwang@redhat.com \
--cc=buermarc@googlemail.com \
--cc=davem@davemloft.net \
--cc=elias.rw2@gmail.com \
--cc=joel.granados@kernel.org \
--cc=kees@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=opurdila@ixiacom.com \
/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.