PT-2026-151759

CVE-2026-99548

·

Published

2026-11-19

·

Updated

2026-11-19

Description by

Score
N/A
Not available

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.

In the Linux kernel, the following vulnerability has been resolved:
smb: client: fix early procfs exposure race
Currently, init cifs() calls cifs proc init() near the beginning of the function, before INIT LIST HEAD, leading to a momentarily uninitialized, but exposed, procfs. If a userspace process reads this empty procfs, iterating over a zeroed list head leads to a NULL pointer dereference and a kernel oops/panic.
For example, if a delay is added between cifs proc init() and INIT LIST HEAD, and a userspace process is polling /proc/fs/cifs/DebugData, the following oops occurs:
BUG: kernel NULL pointer dereference, address: 0000000000000608 Oops: Oops: 0000 [#1] SMP PTI CPU: 0 UID: 0 PID: 3477 Comm: cat Not tainted 7.3.0-02212-g4df4d2a577db-dirty #6 PREEMPT(lazy) RIP: 0010:cifs debug data proc show+0x103/0xd80 [cifs] Call Trace: ? seq read iter+0x86/0x400 ? seq read iter+0x86/0x400 seq read iter+0x183/0x400 proc reg read iter+0x62/0x90 copy splice read+0x215/0x310 splice file to pipe+0xec/0x1c0 do splice+0x4b8/0x780 se sys splice+0x18f/0x250 do syscall 64+0x109/0x330 entry SYSCALL 64 after hwframe+0x77/0x7f
Fix this by moving cifs proc init() down in init cifs(), ensuring it runs only after all internal lists, locks, counters, and workqueues are fully ready, but before registering the filesystem. Update the error cleanup ladder and exit cifs() to maintain proper LIFO order.
Vendors
Affected products
Related identifiers
Found an issue in the description? Have something to add? Feel free to write us 👾