All reports
Medium

kernel: smb: client: Fix next buffer leak in receive_encrypted_standard()

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-64381

Probability of exploitation in the next 30 days: 0.13%

FIRST EPSS · 2026-11-20

Description

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.

A flaw was found in the SMB client of the Linux kernel. A remote attacker could exploit a memory leak in the receive_encrypted_standard() function by sending specially crafted compound Protocol Data Units (PDUs). This vulnerability occurs because a buffer is allocated before a necessary size check, leading to the buffer not being freed if the check fails. Repeated exploitation of this flaw could lead to a Denial of Service (DoS) due to memory exhaustion.