CVE-2026-99548 in Linux
Summary
by MITRE • 11/19/2026
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: <TASK> ? 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 </TASK>
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.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 11/19/2026
The Linux kernel vulnerability identified as a race condition in the Common Internet File System client module involves an improper initialization sequence within the init_cifs function. The core technical flaw lies in the temporal ordering of operations during subsystem startup, specifically where cifs_proc_init is invoked before critical internal data structures are fully initialized. This creates a narrow but exploitable window wherein the procfs interface for CIFS becomes visible to userspace processes while its underlying list heads remain uninitialized or zeroed out. When a privileged user attempts to read from exposed debug interfaces such as /proc/fs/cifs/DebugData during this interval, the kernel attempts to iterate over an empty list head that has not been properly linked into memory structures. This results in a NULL pointer dereference because the iteration logic expects valid pointers but encounters null values due to the premature exposure of the procfs entries before their supporting data structures are ready.
From a technical perspective, this vulnerability represents a classic initialization race condition where resource availability is signaled to external agents prior to internal consistency being achieved. The operational impact manifests as a kernel panic or oops, effectively causing a denial of service for the entire system rather than just the affected subsystem. As evidenced by the provided crash trace, the fault occurs within cifs_debug_data_proc_show when it attempts to access data structures that are not yet valid. This type of issue is particularly dangerous because it requires only local user interaction with specific debug interfaces and can be triggered reliably if timing conditions align, although kernel hardening features like PREEMPT may influence exploitability windows. The vulnerability falls under CWE-362 which covers concurrent execution issues involving shared resources without proper synchronization or ordering guarantees during initialization phases.
The remediation strategy involves reordering the function calls within init_cifs to ensure that all internal lists, locks, counters, and workqueues are fully initialized before cifs_proc_init is executed. This ensures that any procfs entries created by cifs_proc_init point to valid, ready-to-use data structures immediately upon creation. Furthermore, the fix requires updating the error cleanup ladder in init_cifs as well as the exit function exit_cifs to maintain proper Last-In-First-Out ordering during teardown and failure paths. This prevents similar race conditions or use-after-free scenarios that could arise if resources are released before they are no longer accessible by other kernel components or userspace interfaces. By enforcing strict initialization sequencing, the window for exploitation is eliminated entirely since procfs entries will never be exposed until their backing data structures are guaranteed to be valid and stable.
This vulnerability aligns with ATT&CK technique T1059 which involves command execution through system utilities, although in this specific case it leads to local denial of service rather than arbitrary code execution due to the nature of a NULL pointer dereference causing an immediate crash. Mitigation strategies for administrators include ensuring that kernel updates incorporating this fix are applied promptly on systems where CIFS client functionality is enabled and accessible by unprivileged users who might interact with debug interfaces. Additionally, restricting access to /proc filesystem entries through appropriate permissions can reduce the attack surface even before patching occurs. The resolution emphasizes the importance of rigorous initialization ordering in kernel subsystems to prevent transient states from becoming exploitable conditions for local privilege escalation or system instability.