From: Simon Horman <horms@kernel.org>
To: Kees Cook <keescook@chromium.org>
Cc: Justin Stitt <justinstitt@google.com>,
Thomas Sailer <t.sailer@alumni.ethz.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
linux-hams@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v2] hamradio: replace deprecated strncpy with strscpy_pad
Date: Mon, 16 Oct 2023 21:58:36 +0200 [thread overview]
Message-ID: <20231016195836.GB1751252@kernel.org> (raw)
In-Reply-To: <202310161242.B0F9B693@keescook>
On Mon, Oct 16, 2023 at 12:42:22PM -0700, Kees Cook wrote:
> On Mon, Oct 16, 2023 at 06:42:42PM +0000, Justin Stitt wrote:
> > strncpy() is deprecated for use on NUL-terminated destination strings
> > [1] and as such we should prefer more robust and less ambiguous string
> > interfaces.
> >
> > We expect both hi.data.modename and hi.data.drivername to be
> > NUL-terminated based on its usage with sprintf:
> > | sprintf(hi.data.modename, "%sclk,%smodem,fclk=%d,bps=%d%s",
> > | bc->cfg.intclk ? "int" : "ext",
> > | bc->cfg.extmodem ? "ext" : "int", bc->cfg.fclk, bc->cfg.bps,
> > | bc->cfg.loopback ? ",loopback" : "");
> >
> > Note that this data is copied out to userspace with:
> > | if (copy_to_user(data, &hi, sizeof(hi)))
> > ... however, the data was also copied FROM the user here:
> > | if (copy_from_user(&hi, data, sizeof(hi)))
> >
> > Considering the above, a suitable replacement is strscpy_pad() as it
> > guarantees NUL-termination on the destination buffer while also
> > NUL-padding (which is good+wanted behavior when copying data to
> > userspace).
> >
> > Link: https://www.kernel.org/doc/html/latest/process/deprecated.html#strncpy-on-nul-terminated-strings [1]
> > Link: https://github.com/KSPP/linux/issues/90
> > Cc: linux-hardening@vger.kernel.org
> > Signed-off-by: Justin Stitt <justinstitt@google.com>
>
> Thanks!
>
> Reviewed-by: Kees Cook <keescook@chromium.org>
Likewise, thanks. I prefer this over v1.
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2023-10-16 19:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 18:42 [PATCH v2] hamradio: replace deprecated strncpy with strscpy_pad Justin Stitt
2023-10-16 19:42 ` Kees Cook
2023-10-16 19:58 ` Simon Horman [this message]
2023-10-18 1:10 ` patchwork-bot+netdevbpf
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=20231016195836.GB1751252@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=justinstitt@google.com \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-hams@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=t.sailer@alumni.ethz.ch \
/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).