The vulnerability in the Linux kernel SMB client involves a buffer leak in the receive_encrypted_standard() function. The function allocates a next_buffer before verifying if the number of compound PDUs has reached the MAX_COMPOUND limit. If the limit is exceeded, the function returns early without assigning the allocated buffer to the server's buffer pointers, resulting in a memory leak. The patch corrects this by performing the MAX_COMPOUND check prior to buffer allocation, preventing the leak.

This vulnerability causes a memory leak in the Linux kernel SMB client. While it does not directly lead to code execution or privilege escalation, memory leaks can degrade system performance or stability over time. There are no known exploits in the wild for this issue.

The vulnerability has been resolved in the Linux kernel by reordering the check and allocation in the receive_encrypted_standard() function. No specific patch links are provided here; users should apply the latest Linux kernel updates from their vendor or distribution to receive this fix. Patch status is not yet confirmed in this data — check the vendor advisory for current remediation guidance.