From: Viacheslav Dubeyko <slava@dubeyko.com>
To: Michael Bommarito <michael.bommarito@gmail.com>,
Ilya Dryomov <idryomov@gmail.com>, Xiubo Li <xiubli@redhat.com>,
Alex Markuze <amarkuze@redhat.com>
Cc: ceph-devel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] ceph: bound copied dentry name length in NFS export get_name
Date: Mon, 13 Jul 2026 15:18:13 -0700 [thread overview]
Message-ID: <39b2049e2143e72d8b22e3db39a53a4ac1fd88c0.camel@dubeyko.com> (raw)
In-Reply-To: <20260711150706.2915970-1-michael.bommarito@gmail.com>
On Sat, 2026-07-11 at 11:07 -0400, Michael Bommarito wrote:
> ceph_get_name() copies the MDS-supplied name into the caller's
> NAME_MAX-sized buffer with memcpy(name, rinfo->dname, rinfo-
> >dname_len)
> and then writes name[rinfo->dname_len] = 0, without checking
> dname_len
> against NAME_MAX. A malicious or buggy MDS that returns a LOOKUPNAME
> reply
> with dname_len > NAME_MAX overflows the buffer. __get_snap_name()
> copies
> rde->name / rde->name_len the same unchecked way.
>
> Impact: a malicious or compromised Ceph MDS overflows the NAME_MAX
> name
> buffer in a client's NFS-export get_name path, a slab out-of-bounds
> write
> reported by KASAN. Reachable when a CephFS mount is re-exported over
> NFS.
>
> Add ceph_export_copy_name(), which rejects lengths above NAME_MAX
> with
> -ENAMETOOLONG before the copy, and use it in both ceph_get_name() and
> __get_snap_name().
>
> Fixes: 19913b4eac4a ("ceph: add get_name() NFS export callback")
> Cc: stable@vger.kernel.org
> Assisted-by: Claude:claude-opus-4-8
> Signed-off-by: Michael Bommarito <michael.bommarito@gmail.com>
> ---
> fs/ceph/export.c | 26 +++++++++++++++++---------
> 1 file changed, 17 insertions(+), 9 deletions(-)
>
> diff --git a/fs/ceph/export.c b/fs/ceph/export.c
> index b2f2af1046791..debb9634b9e3d 100644
> --- a/fs/ceph/export.c
> +++ b/fs/ceph/export.c
> @@ -442,6 +442,16 @@ static struct dentry *ceph_fh_to_parent(struct
> super_block *sb,
> return dentry;
> }
>
> +static int ceph_export_copy_name(char *name, const char *src, u32
> len)
> +{
> + if (len > NAME_MAX)
> + return -ENAMETOOLONG;
> +
> + memcpy(name, src, len);
> + name[len] = '\0';
> + return 0;
> +}
> +
> static int __get_snap_name(struct dentry *parent, char *name,
> struct dentry *child)
> {
> @@ -513,9 +523,8 @@ static int __get_snap_name(struct dentry *parent,
> char *name,
> BUG_ON(!rde->inode.in);
> if (ceph_snap(inode) ==
> le64_to_cpu(rde->inode.in->snapid)) {
> - memcpy(name, rde->name, rde-
> >name_len);
> - name[rde->name_len] = '\0';
> - err = 0;
> + err = ceph_export_copy_name(name,
> rde->name,
> + rde-
> >name_len);
> goto out;
> }
> }
> @@ -580,8 +589,8 @@ static int ceph_get_name(struct dentry *parent,
> char *name,
>
> rinfo = &req->r_reply_info;
> if (!IS_ENCRYPTED(dir)) {
> - memcpy(name, rinfo->dname, rinfo->dname_len);
> - name[rinfo->dname_len] = 0;
> + err = ceph_export_copy_name(name, rinfo->dname,
> + rinfo->dname_len);
> } else {
> struct fscrypt_str oname = FSTR_INIT(NULL, 0);
> struct ceph_fname fname = { .dir = dir,
> @@ -595,10 +604,9 @@ static int ceph_get_name(struct dentry *parent,
> char *name,
> goto out;
>
> err = ceph_fname_to_usr(&fname, NULL, &oname, NULL);
> - if (!err) {
> - memcpy(name, oname.name, oname.len);
> - name[oname.len] = 0;
> - }
> + if (!err)
> + err = ceph_export_copy_name(name,
> oname.name,
> + oname.len);
> ceph_fname_free_buffer(dir, &oname);
> }
> out:
Looks good from my point of view.
Reviewed-by: Viacheslav Dubeyko <slava@dubeyko.com>
Thanks,
Slava.
prev parent reply other threads:[~2026-07-13 22:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-11 15:07 Michael Bommarito
2026-07-13 22:18 ` Viacheslav Dubeyko [this message]
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=39b2049e2143e72d8b22e3db39a53a4ac1fd88c0.camel@dubeyko.com \
--to=slava@dubeyko.com \
--cc=amarkuze@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.bommarito@gmail.com \
--cc=stable@vger.kernel.org \
--cc=xiubli@redhat.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
all inboxes | Powered by JetHome®