CVE-2026-23282
Received Received - Intake
Uninitialized Variable Causes Kernel Oops in Linux SMB2 Client

Publication date: 2026-03-25

Last updated on: 2026-03-25

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix oops due to uninitialised var in smb2_unlink() If SMB2_open_init() or SMB2_close_init() fails (e.g. reconnect), the iovs set @rqst will be left uninitialised, hence calling SMB2_open_free(), SMB2_close_free() or smb2_set_related() on them will oops. Fix this by initialising @close_iov and @open_iov before setting them in @rqst.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-25
Last Modified
2026-03-25
Generated
2026-05-07
AI Q&A
2026-03-25
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability exists in the Linux kernel's SMB client implementation. It occurs because certain variables related to SMB2 unlink operations are left uninitialized if specific SMB2 functions (SMB2_open_init() or SMB2_close_init()) fail, such as during a reconnect attempt. When these uninitialized variables are later used in functions like SMB2_open_free(), SMB2_close_free(), or smb2_set_related(), it causes the kernel to crash (an oops). The issue is fixed by properly initializing these variables before they are used.


How can this vulnerability impact me? :

This vulnerability can cause the Linux kernel to crash unexpectedly when the SMB client encounters certain failure conditions. Such crashes can lead to system instability, potential denial of service, and disruption of SMB-related network operations.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart