smb: client: Fix next buffer leak in receive_encrypted_standard()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b24df3e30cbf48255db866720fb71f14bf9d2f39 · < 297243e365fc9fe2f8e9b7dd535a65d922cd108b| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
smb: client: Fix next buffer leak in receive_encrypted_standard()
receive_encrypted_standard() allocates next_buffer before checking whether the number of compound PDUs already reached MAX_COMPOUND. If the limit check fails, the function returns immediately and the newly allocated next_buffer is not assigned to server->smallbuf/server->bigbuf, making it leaked.
Move the MAX_COMPOUND check before allocating next_buffer.
From the CVE record · Linux
The Linux kernel SMB client leaks an allocated buffer when receive_encrypted_standard() reaches the MAX_COMPOUND limit. The input does not establish how an attacker could trigger this condition or whether authentication or user interaction is required.
Engineers running Linux kernels with the affected SMB client code should check their installations; affected versions were not provided.