smb: client: fix possible double free in smb2_set_ea()
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 |
|
06.6.596.11.66.12In the Linux kernel, the following vulnerability has been resolved:
smb: client: fix possible double free in smb2_set_ea()
Clang static checker(scan-build) warning: fs/smb/client/smb2ops.c:1304:2: Attempt to free released memory. 1304 | kfree(ea); | ^~~~~~~~~
There is a double free in such case: 'ea is initialized to NULL' -> 'first successful memory allocation for ea' -> 'something failed, goto sea_exit' -> 'first memory release for ea' -> 'goto replay_again' -> 'second goto sea_exit before allocate memory for ea' -> 'second memory release for ea resulted in double free'.
Re-initialie 'ea' to NULL near to the replay_again label, it can fix this double free problem.
From the CVE record · Linux
The Linux kernel SMB client can double-free memory in smb2_set_ea() if an error releases an allocation and a replay path reaches cleanup again before reallocating it. The input does not establish whether an attacker can trigger this condition, or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with the SMB client should check their versions; affected versions are not specified.