CVE-2026-64381

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

State
Published
Severity
Not scored
Published
Jul 25, 2026
Updated
Aug 17, 2026
Reserved
Jul 19, 2026

Read the record on cve.org

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.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • b24df3e30cbf48255db866720fb71f14bf9d2f39 to before 94e4f672db029414b9888b5137a7559f1febf2d8Affected
  • b24df3e30cbf48255db866720fb71f14bf9d2f39 to before 68fc0b6cc03ca58060c0f36454e169f5fe258974Affected
  • b24df3e30cbf48255db866720fb71f14bf9d2f39 to before 07e0ab81df1790afa35732a4e8e07ff831b29008Affected
  • b24df3e30cbf48255db866720fb71f14bf9d2f39 to before 9136a08dc29328edd9867f2545e73906ac9df93bAffected
  • b24df3e30cbf48255db866720fb71f14bf9d2f39 to before 67097772df7791c53d608f04bd31c676ccf79b83Affected
  • b24df3e30cbf48255db866720fb71f14bf9d2f39 to before 297243e365fc9fe2f8e9b7dd535a65d922cd108bAffected
  • b24df3e30cbf48255db866720fb71f14bf9d2f39 to before 927d4805aea0a287d36dd4f826ee24d69a2afee3Affected
  • b24df3e30cbf48255db866720fb71f14bf9d2f39 to before 1c6267a1d5cf4c73b656f8181b310cbbb3e4767bAffected
LinuxLinux
  • 4.19Affected
  • before 4.19Not affected
  • 5.10.261 through 5.10.*Not affected
  • 5.15.212 through 5.15.*Not affected
  • 6.1.178 through 6.1.*Not affected
  • 6.6.145 through 6.6.*Not affected
  • 6.12.96 through 6.12.*Not affected
  • 6.18.39 through 6.18.*Not affected
  • 7.1.4 through 7.1.*Not affected
  • 7.2 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.