PT-2026-151773

CVE-2026-99562

·

تاريخ النشر

2026-11-19

·

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

2026-11-19

الوصف من

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

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

In the Linux kernel, the following vulnerability has been resolved:
ksmbd: reject FSCTL SET ZERO DATA on a directory handle
An authenticated client with a writable tree connection can open a directory with FILE WRITE DATA and send FSCTL SET ZERO DATA on that handle. The handler only checks fp->daccess & FILE WRITE DATA LE, but on a directory FILE WRITE DATA is the legitimate add-file right, so the check passes. ksmbd vfs zero data() then calls kernel write() on the directory file, which has no FMODE WRITE, and kernel write iter() hits WARN ON ONCE(!(file->f mode & FMODE WRITE)), panicking a panic on warn kernel.
Before commit 25e414db7033 ("ksmbd: report holes in allocated range queries") the dense-file path used vfs fallocate(), which rejects directories with -EISDIR. The kernel write() loop that replaced it has no such check. Reject a directory handle in ksmbd vfs zero data() before writing, as ksmbd vfs write() already does for SMB2 WRITE.
WARNING: fs/read write.c:608 at kernel write iter+0x74b/0x8c0 Workqueue: ksmbd-io handle ksmbd work Call Trace: kernel write+0x1ef/0x4d0 ksmbd vfs zero data+0x413/0x590 smb2 ioctl+0x21fa/0x66a0 handle ksmbd work+0x61b/0x1ff0
المورّدون
المنتجات المتأثرة
المعرّفات ذات الصلة
وجدت خطأً في الوصف؟ لديك ما تضيفه؟ لا تتردد في مراسلتنا 👾