]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
fuse: prevent overflow in copy_file_range return value
authorMiklos Szeredi <mszeredi@redhat.com>
Tue, 12 Aug 2025 12:46:34 +0000 (14:46 +0200)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 19 Sep 2025 14:37:31 +0000 (16:37 +0200)
commit24e5758a5371bbf422c2e4a183f0029c1be1e59d
tree20d8a707f33f720339a9de5ec68e1a9645c3671d
parentb74616c44326d00adead506fa4a050457500a52e
fuse: prevent overflow in copy_file_range return value

commit 1e08938c3694f707bb165535df352ac97a8c75c9 upstream.

The FUSE protocol uses struct fuse_write_out to convey the return value of
copy_file_range, which is restricted to uint32_t.  But the COPY_FILE_RANGE
interface supports a 64-bit size copies.

Currently the number of bytes copied is silently truncated to 32-bit, which
may result in poor performance or even failure to copy in case of
truncation to zero.

Reported-by: Florian Weimer <fweimer@redhat.com>
Closes: https://lore.kernel.org/all/lhuh5ynl8z5.fsf@oldenburg.str.redhat.com/
Fixes: 88bc7d5097a1 ("fuse: add support for copy_file_range()")
Cc: <stable@vger.kernel.org> # v4.20
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/fuse/file.c