CVE-2023-54162: 
Linux Debian vulnerability analysis and mitigation

CVE-2023-54162 is a memory leak vulnerability in the Linux kernel's ksmbd (kernel SMB server) subsystem, specifically within the smb2_lock() function. The flaw occurs because the argv buffer is not freed when setup_async_work fails or when the current process is woken up, resulting in a possible memory leak. It affects the Linux kernel and was published on December 30, 2025. No CVSS score has been assigned by NVD at this time, and the record is not currently prioritized for NVD enrichment (NVD).

The root cause is improper memory management (CWE not formally assigned, but consistent with CWE-401: Missing Release of Memory after Effective Lifetime) in the ksmbd subsystem's smb2_lock() function. When setup_async_work() fails or the process is woken up during an SMB2 lock operation, the argv allocation is not released, leading to a kernel memory leak. This is a local or network-triggered issue depending on how ksmbd is exposed, as ksmbd handles SMB2 protocol requests from network clients. Fixes have been submitted to the stable kernel tree across multiple branches (NVD, kernel.org patch 1, kernel.org patch 2).

The primary impact of this vulnerability is a kernel memory leak, which over time can degrade system availability by exhausting kernel memory resources on systems running ksmbd as an SMB server. There is no direct evidence of confidentiality or integrity compromise; however, sustained memory exhaustion could lead to denial-of-service conditions on affected servers. Systems actively serving SMB2 clients via ksmbd are most at risk (NVD).

There is no known public exploit code, active in-the-wild exploitation, or threat actor attribution associated with CVE-2023-54162. The EPSS score is approximately 0.018% (0.000180), indicating a very low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog (Feedly).

The Linux kernel stable tree has received patches addressing this memory leak across multiple stable branches. Administrators should apply the relevant kernel updates containing the following commits: 11d38f8a0c19763e34d2093b5ecb640e012cb2d2, 6bf555ed8938444466c3d7f3252eb874a518f293, bfe8372ef2dbdce97f13b21d76e2080ddeef5a79, and d3ca9f7aeba793d74361d88a8800b2f205c9236b. Systems not using ksmbd can mitigate risk by disabling or not loading the ksmbd kernel module. Distribution-specific kernel updates should be monitored and applied promptly (NVD).