Re: [PATCH v2 0/5] smb: server: Clear sensitive data before freeing it

Namjae Jeon <[email protected]>
Newsgroups org.kernel.vger.linux-kernel
Message-ID <CAKYAXd_Ja0HaxcUYyFSt6wj0GakbJBNz96fc1QoT-zjuPNP3ow@mail.gmail.com>
On Wed, Aug 12, 2026 at 12:46 AM Thomas Huth <[email protected]> wrote:
>
> Sensitive data like keys that are stored in stack-local arrays could be
> leaked via the stack to the calling functions, or via the heap when using
> only normal kfree() functions.
>
> It's good security practice to clear sensitive data on the stack first
> with memzero_explicit() before leaving the context, and to use
> kfree_sensitive() for data that is returned to the heap.
>
> Disclaimer: The spots that need clearing have been identified with AI,
> but the patches have been created manually (for double-checking whether
> the findings really make sense). Anyway, I'm not very familiar with the
> smb code, so please review carefully. Thanks!
>
> v2:
> - Calculate proper size for the kvfree_sensitive() in the first patch
> - Add "kfree_sensitive(target)" hunk to the connection.c patch
> - Add patch to clear Preauth_HashValue in smb2pdu.c
Applied them to #ksmbd-for-next-next.
Thanks!
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.