PT-2026-148137

CVE-2026-99293

·

تاريخ النشر

2026-11-16

·

تاريخ التحديث

2026-11-16

الوصف من

الدرجة
N/A
غير متوفر

لا تتوفر حاليًا تقييمات أو مقاييس للخطورة. سنحدّث المعلومات المقابلة في الصفحة فور توفرها.

In the Linux kernel, the following vulnerability has been resolved:
fuse: don't BUG when the copy buffer is exhausted
fuse copy fill() hits BUG ON(!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:fuse copy fill (fs/fuse/dev.c:1033) Call Trace: fuse copy args (fs/fuse/dev.c:1354 fs/fuse/dev.c:1380) fuse uring args to ring (fs/fuse/dev uring.c:891) fuse uring prepare send (fs/fuse/dev uring.c:940 fs/fuse/dev uring.c:1057) fuse uring send in task (fs/fuse/dev uring.c:1745) tctx task work run (io uring/tw.c:96) tctx task work (io uring/tw.c:133) task work run (kernel/task work.c:233) io run task work (io uring/tw.h:84) io cqring wait (io uring/wait.c:278) do sys io uring enter (io uring/io uring.c:2676) do syscall 64 (arch/x86/entry/syscall 64.c:61) entry SYSCALL 64 after hwframe (arch/x86/entry/entry 64.S:121)
The reply path can drain it the same way, via the server-supplied payload sz in fuse uring copy from ring().
Return -EIO instead. All three fuse copy fill() callers already propagate the error.
المورّدون
المنتجات المتأثرة
المعرّفات ذات الصلة
وجدت خطأً في الوصف؟ لديك ما تضيفه؟ لا تتردد في مراسلتنا 👾