[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <168478437626.244538.6559937483217152450.b4-ty@chromium.org>
Date: Mon, 22 May 2023 12:39:42 -0700
From: Kees Cook <keescook@...omium.org>
To: rostedt@...dmis.org, mhiramat@...nel.org, azeemshaikh38@...il.com
Cc: Kees Cook <keescook@...omium.org>,
linux-trace-kernel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-hardening@...r.kernel.org
Subject: Re: [PATCH v2] tracing: Replace all non-returning strlcpy with strscpy
On Tue, 16 May 2023 14:39:56 +0000, Azeem Shaikh wrote:
> strlcpy() reads the entire source buffer first.
> This read may exceed the destination size limit.
> This is both inefficient and can lead to linear read
> overflows if a source string is not NUL-terminated [1].
> In an effort to remove strlcpy() completely [2], replace
> strlcpy() here with strscpy().
>
> [...]
Applied to for-next/hardening, thanks!
[1/1] tracing: Replace all non-returning strlcpy with strscpy
https://git.kernel.org/kees/c/4cb4e5158b89
--
Kees Cook
Powered by blists - more mailing lists