From: Bernd Schubert <bernd@bsbernd.com>
To: Xiang Mei <xmei5@asu.edu>, Joanne Koong <joannelkoong@gmail.com>,
djwong@kernel.org, Miklos Szeredi <miklos@szeredi.hu>,
Kees Cook <kees@kernel.org>,
"Gustavo A . R . Silva" <gustavoars@kernel.org>
Cc: stable@vger.kernel.org, fuse-devel@lists.linux.dev,
linux-kernel@vger.kernel.org,
Pavel Begunkov <asml.silence@gmail.com>,
Luis Henriques <luis@igalia.com>,
Weiming Shi <bestswngs@gmail.com>
Subject: Re: [PATCH v2 1/2] fuse: copy request headers via a stack buffer for io-uring
Date: Wed, 8 Jul 2026 22:21:30 +0200 [thread overview]
Message-ID: <1227637e-c9b6-4bcb-ba91-dfe896e5c310@bsbernd.com> (raw)
In-Reply-To: <20260707184417.3682270-1-xmei5@asu.edu>
On 7/7/26 20:44, Xiang Mei wrote:
> The fuse-io-uring transport copies req->in.h out to the ring in
> fuse_uring_copy_to_ring() and req->out.h back in fuse_uring_commit().
> Both headers live inside the fuse_request slab object, whose cache
> (fuse_req_cachep) is created without a usercopy whitelist, so copying
> them directly to/from userspace trips CONFIG_HARDENED_USERCOPY and
> panics:
>
> usercopy: Kernel memory exposure attempt detected from SLUB object
> 'fuse_request' (offset 56, size 40)!
> kernel BUG at mm/usercopy.c:102!
> RIP: 0010:usercopy_abort+0x6c/0x80
> Call Trace:
> __check_heap_object
> __check_object_size
> copy_header_to_ring fs/fuse/dev_uring.c:618
> fuse_uring_prepare_send
> fuse_uring_send_in_task
> ...
> __do_sys_io_uring_enter
> entry_SYSCALL_64_after_hwframe
>
> Bounce both headers through an on-stack copy so the usercopy touches
> stack memory, not the slab object.
>
> Fixes: c090c8abae4b ("fuse: Add io-uring sqe commit and fetch support")
> Cc: stable@vger.kernel.org
> Reported-by: Weiming Shi <bestswngs@gmail.com>
> Assisted-by: Claude:claude-opus-4-8
> Signed-off-by: Xiang Mei <xmei5@asu.edu>
> Reviewed-by: Joanne Koong <joannelkoong@gmail.com>
> ---
> v2: add: Cc stable and Reviewed-by tags
>
> fs/fuse/dev_uring.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/fs/fuse/dev_uring.c b/fs/fuse/dev_uring.c
> index 77c8cec43d9c..0814681eb04b 100644
> --- a/fs/fuse/dev_uring.c
> +++ b/fs/fuse/dev_uring.c
> @@ -744,6 +744,7 @@ static int fuse_uring_copy_to_ring(struct fuse_ring_ent *ent,
> {
> struct fuse_ring_queue *queue = ent->queue;
> struct fuse_ring *ring = queue->ring;
> + struct fuse_in_header in_header;
> int err;
>
> err = -EIO;
> @@ -765,8 +766,9 @@ static int fuse_uring_copy_to_ring(struct fuse_ring_ent *ent,
> }
>
> /* copy fuse_in_header */
> - return copy_header_to_ring(ent, FUSE_URING_HEADER_IN_OUT, &req->in.h,
> - sizeof(req->in.h));
> + in_header = req->in.h;
> + return copy_header_to_ring(ent, FUSE_URING_HEADER_IN_OUT, &in_header,
> + sizeof(in_header));
> }
>
> static int fuse_uring_prepare_send(struct fuse_ring_ent *ent,
> @@ -871,11 +873,13 @@ static void fuse_uring_commit(struct fuse_ring_ent *ent, struct fuse_req *req,
> unsigned int issue_flags)
> {
> struct fuse_ring *ring = ent->queue->ring;
> + struct fuse_out_header out_header;
> ssize_t err = -EFAULT;
>
> - if (copy_header_from_ring(ent, FUSE_URING_HEADER_IN_OUT, &req->out.h,
> - sizeof(req->out.h)))
> + if (copy_header_from_ring(ent, FUSE_URING_HEADER_IN_OUT, &out_header,
> + sizeof(out_header)))
> goto out;
> + req->out.h = out_header;
>
> err = fuse_uring_out_header_has_err(&req->out.h, req);
> if (err) {
Reviewed-by: Bernd Schubert <bernd@bsbernd.com>
prev parent reply other threads:[~2026-07-08 20:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 18:44 Xiang Mei
2026-07-07 18:44 ` [PATCH v2 2/2] fuse: reject oversized payload_sz in fuse_uring_copy_from_ring() Xiang Mei
2026-07-08 19:22 ` Bernd Schubert
2026-07-08 23:08 ` Joanne Koong
2026-07-09 21:16 ` Xiang Mei
2026-07-08 20:21 ` Bernd Schubert [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=1227637e-c9b6-4bcb-ba91-dfe896e5c310@bsbernd.com \
--to=bernd@bsbernd.com \
--cc=asml.silence@gmail.com \
--cc=bestswngs@gmail.com \
--cc=djwong@kernel.org \
--cc=fuse-devel@lists.linux.dev \
--cc=gustavoars@kernel.org \
--cc=joannelkoong@gmail.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luis@igalia.com \
--cc=miklos@szeredi.hu \
--cc=stable@vger.kernel.org \
--cc=xmei5@asu.edu \
/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®