linux-kernel - Re: [PATCH] params: Replace deprecated strcpy() with strscpy()

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <F640B308-C8C4-439B-8217-98FFC10BB76B@linux.dev>
Date: Wed, 13 Aug 2025 11:33:18 +0200
From: Thorsten Blum <thorsten.blum@...ux.dev>
To: Petr Pavlu <petr.pavlu@...e.com>
Cc: Thomas Weißschuh <linux@...ssschuh.net>,
 Shyam Saini <shyamsaini@...ux.microsoft.com>,
 Luis Chamberlain <mcgrof@...nel.org>,
 Dmitry Antipov <dmantipov@...dex.ru>,
 linux-kernel@...r.kernel.org,
 linux-modules@...r.kernel.org
Subject: Re: [PATCH] params: Replace deprecated strcpy() with strscpy()

Hi Petr,

On 13. Aug 2025, at 10:59, Petr Pavlu wrote:
> Since the code already calculated the length of val and that it fits
> into kps->string, is there any advantage (or disadvantage) to using
> strscpy() over memcpy()?

strscpy() guarantees that the destination buffer 'kps->string' is always
NUL-terminated, even if the source 'val' is not. memcpy() just copies
the bytes as they are.

If it were guaranteed that 'val' is always NUL-terminated, memcpy()
would be fine too, but since param_set_copystring() is exported, we
probably can't make that assumption.

> I think this can go through the modules tree. I've CC'd the mailing
> list.

Thanks,
Thorsten