PT-2026-151764

CVE-2026-99553

·

تاريخ النشر

2026-11-19

·

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

2026-11-19

الوصف من

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

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

In the Linux kernel, the following vulnerability has been resolved:
nfsd: fix race between client info show() and free client()
client info show() renders /proc/fs/nfsd/clients//info and walks clp->cl sessions under clp->cl lock to print each session's slot counts. free client() tears down the same list without taking cl lock, and is the only unlocked mutator of cl sessions. A reader can observe a client mid-teardown because get nfsdfs clp() pins the nfs4 client but not its sessions: free client() frees every session before calling nfsd client rmdir(), so an in-flight seq file reader can follow a list del()'d node whose ->next now holds LIST POISON1 and take a general protection fault:
Oops: general protection fault, probably for non-canonical address 0xdead00000000014c CPU: 1 UID: 0 PID: 132488 Comm: cat RIP: 0010:client info show+0x2bf/0x3d0 RAX: dead000000000100 Call Trace: seq read iter+0x12a/0x4b0 seq read+0xf1/0x130 vfs read+0xbf/0x350 ksys read+0x6f/0xf0 do syscall 64+0x8b/0xcb0 entry SYSCALL 64 after hwframe+0x76/0x7e Kernel panic - not syncing: Fatal exception
Detach cl sessions onto a local reaplist under cl lock, then free the sessions after dropping the lock. Removing entries from cl sessions under cl lock matches unhash session(), and the detach-then-reap shape matches how destroy client() reaps cl delegations. The sessions cannot be freed while cl lock is held, since free session() calls nfsd4 del conns(), which re-acquires it.
المورّدون
المنتجات المتأثرة
المعرّفات ذات الصلة
وجدت خطأً في الوصف؟ لديك ما تضيفه؟ لا تتردد في مراسلتنا 👾