cifs: fix potential null pointer use in destroy_workqueue in init_cifs error path
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
cifs: fix potential null pointer use in destroy_workqueue in init_cifs error path
Dan Carpenter reported a Smack static checker warning: fs/smb/client/cifsfs.c:1981 init_cifs() error: we previously assumed 'serverclose_wq' could be null (see line 1895)
The patch which introduced the serverclose workqueue used the wrong oredering in error paths in init_cifs() for freeing it on errors.
From the CVE record · Linux
The Linux kernel CIFS client has incorrect workqueue cleanup ordering in an init_cifs() error path, potentially causing a null pointer use. The input does not describe how an attacker could trigger the error or specify network access, authentication, or user-interaction requirements.
Engineers running the Linux kernel should check affected versions against the vendor advisory; no versions are specified in the input.