From: Luis Chamberlain <mcgrof@kernel.org>
To: Kees Cook <keescook@chromium.org>
Cc: Ondrej Mosnacek <omosnace@redhat.com>,
Iurii Zaikin <yzaikin@google.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sysctl: fix proc_dobool() usability
Date: Tue, 21 Feb 2023 13:36:31 -0800 [thread overview]
Message-ID: <Y/U5X5F0iFcpLwRK@bombadil.infradead.org> (raw)
In-Reply-To: <63f500ba.170a0220.c76fc.1642@mx.google.com>
On Tue, Feb 21, 2023 at 09:34:49AM -0800, Kees Cook wrote:
> On Fri, Feb 10, 2023 at 03:58:23PM +0100, Ondrej Mosnacek wrote:
> > Currently proc_dobool expects a (bool *) in table->data, but sizeof(int)
> > in table->maxsize, because it uses do_proc_dointvec() directly.
> >
> > This is unsafe for at least two reasons:
> > 1. A sysctl table definition may use { .data = &variable, .maxsize =
> > sizeof(variable) }, not realizing that this makes the sysctl unusable
> > (see the Fixes: tag) and that they need to use the completely
> > counterintuitive sizeof(int) instead.
> > 2. proc_dobool() will currently try to parse an array of values if given
> > .maxsize >= 2*sizeof(int), but will try to write values of type bool
> > by offsets of sizeof(int), so it will not work correctly with neither
> > an (int *) nor a (bool *). There is no .maxsize validation to prevent
> > this.
> >
> > Fix this by:
> > 1. Constraining proc_dobool() to allow only one value and .maxsize ==
> > sizeof(bool).
> > 2. Wrapping the original struct ctl_table in a temporary one with .data
> > pointing to a local int variable and .maxsize set to sizeof(int) and
> > passing this one to proc_dointvec(), converting the value to/from
> > bool as needed (using proc_dou8vec_minmax() as an example).
> > 3. Extending sysctl_check_table() to enforce proc_dobool() expectations.
> > 4. Fixing the proc_dobool() docstring (it was just copy-pasted from
> > proc_douintvec, apparently...).
> > 5. Converting all existing proc_dobool() users to set .maxsize to
> > sizeof(bool) instead of sizeof(int).
> >
> > Fixes: 83efeeeb3d04 ("tty: Allow TIOCSTI to be disabled")
> > Fixes: a2071573d634 ("sysctl: introduce new proc handler proc_dobool")
> > Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
>
> Ah nice, thanks for tracking this down.
>
> Acked-by: Kees Cook <keescook@chromium.org>
Queued onto sysctl-next, will send to Linus as this is a fix too.
Luis
next prev parent reply other threads:[~2023-02-21 21:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 14:58 [PATCH] sysctl: fix proc_dobool() usability Ondrej Mosnacek
2023-02-20 12:52 ` Ondrej Mosnacek
2023-02-21 17:34 ` Kees Cook
2023-02-21 21:36 ` Luis Chamberlain [this message]
2023-02-22 7:52 ` Ondrej Mosnacek
2023-03-05 2:18 ` Request to backport "sysctl: fix proc_dobool() usability" to stable kernels Thomas Weißschuh
2023-03-05 2:51 ` Storm Dragon
2023-03-05 3:06 ` Thomas Weißschuh
2023-03-06 17:47 ` Storm Dragon
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=Y/U5X5F0iFcpLwRK@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=omosnace@redhat.com \
--cc=yzaikin@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).