CVE-2026-64381
Medium
Elevated severity or exploit probability.
CVSS base
7.8
HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS — probability of exploitation (30 days)
0.1%
3.0th percentile
CISA KEV
Not listed
Weakness / dates
CWE-787
Published 2026-07-25 · modified 2026-09-08
CVSS breakdown
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
| Attack Vector | L | Local |
| Attack Complexity | L | Low |
| Privileges Required | L | Low |
| User Interaction | N | None |
| Scope | U | Unchanged |
| Confidentiality | H | High |
| Integrity | H | High |
| Availability | H | High |
Timeline
- 2026-07-25 — Published (NVD)
- 2026-09-08 — Last modified (NVD)
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.
Affected
References
- https://git.kernel.org/stable/c/07e0ab81df1790afa35732a4e8e07ff831b29008
- https://git.kernel.org/stable/c/1c6267a1d5cf4c73b656f8181b310cbbb3e4767b
- https://git.kernel.org/stable/c/297243e365fc9fe2f8e9b7dd535a65d922cd108b
- https://git.kernel.org/stable/c/67097772df7791c53d608f04bd31c676ccf79b83
- https://git.kernel.org/stable/c/68fc0b6cc03ca58060c0f36454e169f5fe258974
- https://git.kernel.org/stable/c/9136a08dc29328edd9867f2545e73906ac9df93b
- https://git.kernel.org/stable/c/927d4805aea0a287d36dd4f826ee24d69a2afee3
- https://git.kernel.org/stable/c/94e4f672db029414b9888b5137a7559f1febf2d8