The Linux kernel’s SMB server initialization routine incorrectly continues when the process‑setup step fails. A null pointer dereference during counter reset causes a kernel panic, which results in a denial‑of‑service condition. The vulnerability is an instance of a null‑pointer dereference weakness (CWE‑476). The crash occurs after a userspace client initiates the server, so the likely attack vector is a remote SMB connection that triggers the server startup path. The impact is that a single malformed or unclean SMB session can bring the entire host down, potentially affecting availability for all users and services hosted on the affected machine. The fault is exposed on all Linux systems that build the ksmbd kernel module, regardless of distribution, as the kernel source is common to all releases. No specific version numbers are provided, so any kernel that has not yet been patched for this issue is vulnerable. Risk assessment indicates that the EPSS score is below 1%, showing a low predicted exploitation probability in the wild. The vulnerability is not listed in the CISA KEV catalog and the CVSS severity is not disclosed in the supplied data. However, because the flaw leads directly to a kernel panic, the potential loss of availability is high, but practical exploitation is considered unlikely without a committed attacker. }

All Linux kernels that include the ksmbd SMB server module are affected. The vulnerability is present in the kernel source regardless of distribution (Linux:Linux). No specific product versions are identified in the report, so all installations lacking a recent patch are potentially vulnerable.

The flaw is a low‑probability but high‑impact kernel‑panic condition caused by a null‑pointer dereference during SMB server start‑up. The EPSS score of less than 1% suggests that attacks are not widely observed, and the vulnerability is not yet featured in the CISA KEV catalog. Nonetheless, the CVE demonstrates a direct path from a remote SMB client to a kernel crash; systems that expose an SMB server should treat this as a critical availability risk.