CVE-2026-64381 Details
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 buffer leak vulnerability has been identified in the Linux kernel's SMB client implementation, specifically within the 'receive_encrypted_standard' function of the SMB2 operations. This vulnerability arises because the function allocates a buffer for the next command before verifying whether the number of compound Protocol Data Units (PDUs) has reached the maximum limit. If the limit is exceeded, the function exits prematurely, causing the newly allocated buffer to be lost and unutilized, which leads to a memory leak. The issue has been addressed by repositioning the limit check to occur before the buffer allocation, ensuring that the buffer is only allocated when it can be properly managed.
Users can upgrade to the latest version of the Linux kernel where this vulnerability has been fixed. Instructions for downloading the patched version are available on the official Linux kernel website.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/07e0ab81df1790afa35732a4e8e07ff831b29008 | kernel.org | Patch |
| https://git.kernel.org/stable/c/1c6267a1d5cf4c73b656f8181b310cbbb3e4767b | kernel.org | Patch |
| https://git.kernel.org/stable/c/297243e365fc9fe2f8e9b7dd535a65d922cd108b | kernel.org | Patch |
| https://git.kernel.org/stable/c/67097772df7791c53d608f04bd31c676ccf79b83 | kernel.org | Patch |
| https://git.kernel.org/stable/c/68fc0b6cc03ca58060c0f36454e169f5fe258974 | kernel.org | Patch |
| https://git.kernel.org/stable/c/9136a08dc29328edd9867f2545e73906ac9df93b | kernel.org | Patch |
| https://git.kernel.org/stable/c/927d4805aea0a287d36dd4f826ee24d69a2afee3 | kernel.org | Patch |
| https://git.kernel.org/stable/c/94e4f672db029414b9888b5137a7559f1febf2d8 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-787 | Out-of-bounds Write | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 4.19, < 5.10.261 >= 5.11, < 5.15.212 >= 5.16, < 6.1.178 >= 6.2, < 6.6.145 >= 6.7, < 6.12.96 >= 6.13, < 6.18.39 >= 6.19, < 7.1.4 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Sep 8, 2026 | Initial Analysis | [email protected] |
| Aug 17, 2026 | CVE Modified | kernel.org |
| Jul 25, 2026 | New CVE Received | kernel.org |