From: Trond Myklebust <trondmy@hammerspace.com>
To: "anna@kernel.org" <anna@kernel.org>,
"zichenxie0106@gmail.com" <zichenxie0106@gmail.com>,
"bcodding@redhat.com" <bcodding@redhat.com>
Cc: "zzjas98@gmail.com" <zzjas98@gmail.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"chenyuan0y@gmail.com" <chenyuan0y@gmail.com>
Subject: Re: [PATCH] NFS: Fix potential buffer overflowin nfs_sysfs_link_rpc_client()
Date: Tue, 17 Dec 2024 16:51:21 +0000 [thread overview]
Message-ID: <41572d6005dfb2042482f98177a9b295433c8a5f.camel@hammerspace.com> (raw)
In-Reply-To: <20241217161311.28640-1-zichenxie0106@gmail.com>
On Wed, 2024-12-18 at 00:13 +0800, Gax-c wrote:
> From: Zichen Xie <zichenxie0106@gmail.com>
>
> name is char[64] where the size of clnt->cl_program->name remains
> unknown. Invoking strcat() directly will also lead to potential
> buffer
> overflow. Change them to strscpy() and strncat() to fix potential
> issues.
What makes you think that clnt->cl_program->name is unknown?
All calls to nfs_sysfs_link_rpc_client() use well known RPC clients for
which the cl_program is pointing to one of nlm_program, nfs_program or
nfsacl_program. So we know very well the sizes of clnt->cl_program-
>name.
>
> Fixes: e13b549319a6 ("NFS: Add sysfs links to sunrpc clients for
> nfs_clients")
> Signed-off-by: Zichen Xie <zichenxie0106@gmail.com>
> Cc: stable@vger.kernel.org
> ---
> fs/nfs/sysfs.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/fs/nfs/sysfs.c b/fs/nfs/sysfs.c
> index bf378ecd5d9f..7b59a40d40c0 100644
> --- a/fs/nfs/sysfs.c
> +++ b/fs/nfs/sysfs.c
> @@ -280,9 +280,9 @@ void nfs_sysfs_link_rpc_client(struct nfs_server
> *server,
> char name[RPC_CLIENT_NAME_SIZE];
> int ret;
>
> - strcpy(name, clnt->cl_program->name);
> - strcat(name, uniq ? uniq : "");
> - strcat(name, "_client");
> + strscpy(name, clnt->cl_program->name, sizeof(name));
> + strncat(name, uniq ? uniq : "", sizeof(name) - strlen(name)
> - 1);
> + strncat(name, "_client", sizeof(name) - strlen(name) - 1);
>
> ret = sysfs_create_link_nowarn(&server->kobj,
> &clnt->cl_sysfs-
> >kobject, name);
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2024-12-17 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 16:13 [PATCH] NFS: Fix potential buffer overflowin nfs_sysfs_link_rpc_client() Gax-c
2024-12-17 16:51 ` Trond Myklebust [this message]
2024-12-17 17:07 ` Trond Myklebust
2024-12-18 14:28 ` Benjamin Coddington
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=41572d6005dfb2042482f98177a9b295433c8a5f.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=anna@kernel.org \
--cc=bcodding@redhat.com \
--cc=chenyuan0y@gmail.com \
--cc=linux-nfs@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=zichenxie0106@gmail.com \
--cc=zzjas98@gmail.com \
/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