smb: client: fix oops due to uninitialised var in smb2_unlink()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.176.19.77.0In 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.
From the CVE record · Linux
The Linux kernel SMB client can crash when SMB2_open_init() or SMB2_close_init() fails, such as during a reconnect, leaving request data uninitialised. The input does not specify whether an attacker can trigger this condition or whether authentication or user interaction is required.
Engineers running Linux systems that use the kernel SMB client should check their kernel; affected versions are not specified.