CVE-2026-99293: fuse: don't BUG when the copy buffer is exhausted
In the Linux kernel, the following vulnerability has been resolved:
fuse: don't BUG when the copy buffer is exhausted
fusecopyfill() hits BUGON(!err) once the iterator backing the copy runs out of pages. Over io-uring the amount copied is not bounded by the payload buffer the server registered, so an unprivileged user can drain the iterator and panic the host - mount a FUSE filesystem with small payload buffers, then setxattr() a larger value:
kernel BUG at fs/fuse/dev.c:1064! Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI CPU: 1 UID: 0 PID: 148 Comm: exploit Not tainted 7.3.0-rc1 #2 RIP: 0010:fusecopyfill (fs/fuse/dev.c:1033) Call Trace: <TASK> fusecopyargs (fs/fuse/dev.c:1354 fs/fuse/dev.c:1380) fuseuringargstoring (fs/fuse/devuring.c:891) fuseuringpreparesend (fs/fuse/devuring.c:940 fs/fuse/devuring.c:1057) fuseuringsendintask (fs/fuse/devuring.c:1745) tctxtaskworkrun (iouring/tw.c:96) tctxtaskwork (iouring/tw.c:133) taskworkrun (kernel/taskwork.c:233) ioruntaskwork (iouring/tw.h:84) iocqringwait (iouring/wait.c:278) dosysiouringenter (iouring/iouring.c:2676) dosyscall64 (arch/x86/entry/syscall64.c:61) entrySYSCALL64afterhwframe (arch/x86/entry/entry64.S:121)
The reply path can drain it the same way, via the server-supplied payloadsz in fuseuringcopyfromring().
Return -EIO instead. All three fusecopyfill() callers already propagate the error.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Compensating control
In the Linux FUSE code, return -EIO instead of triggering BUG when fuse_copy_fill() exhausts the copy buffer, and propagate the error through the callers.