[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <168478437621.244538.1202856406180337699.b4-ty@chromium.org>
Date: Mon, 22 May 2023 12:39:43 -0700
From: Kees Cook <keescook@...omium.org>
To: hdegoede@...hat.com, azeemshaikh38@...il.com
Cc: Kees Cook <keescook@...omium.org>, linux-kernel@...r.kernel.org,
linux-hardening@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH] vboxsf: Replace all non-returning strlcpy with strscpy
On Wed, 10 May 2023 21:11:46 +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().
> No return values were used, so direct replacement is safe.
>
> [...]
Applied to for-next/hardening, thanks!
[1/1] vboxsf: Replace all non-returning strlcpy with strscpy
https://git.kernel.org/kees/c/883f8fe87686
--
Kees Cook
Powered by blists - more mailing lists