---
id: CVE-2026-64381
title: |-
  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 PDU…
summary: |-
  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 PDU…
severity: high
cvss: 7.8
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'
cwe:
  - CWE-787
  - CWE-772
vendor: linux
product: linux_kernel
affected:
  - 'linux_kernel >= 4.19, < 5.10.261'
  - 'linux_kernel >= 5.11, < 5.15.212'
  - 'linux_kernel >= 5.16, < 6.1.178'
  - 'linux_kernel >= 6.2, < 6.6.145'
  - 'linux_kernel >= 6.7, < 6.12.96'
  - 'linux_kernel >= 6.13, < 6.18.39'
  - 'linux_kernel >= 6.19, < 7.1.4'
patched:
  - linux_kernel 7.1.4
published: '2026-07-25'
updated: '2026-09-08'
sourceUpdated: '2026-09-08T14:01:34.767'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-64381'
references:
  - url: 'https://git.kernel.org/stable/c/07e0ab81df1790afa35732a4e8e07ff831b29008'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/1c6267a1d5cf4c73b656f8181b310cbbb3e4767b'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/297243e365fc9fe2f8e9b7dd535a65d922cd108b'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/67097772df7791c53d608f04bd31c676ccf79b83'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/68fc0b6cc03ca58060c0f36454e169f5fe258974'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/9136a08dc29328edd9867f2545e73906ac9df93b'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/927d4805aea0a287d36dd4f826ee24d69a2afee3'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/94e4f672db029414b9888b5137a7559f1febf2d8'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: >-
      https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-64381.json
  - url: 'https://access.redhat.com/security/cve/CVE-2026-64381'
  - url: 'https://bugzilla.redhat.com/show_bug.cgi?id=2507108'
  - url: 'https://www.cve.org/CVERecord?id=CVE-2026-64381'
  - url: 'https://nvd.nist.gov/vuln/detail/CVE-2026-64381'
  - url: >-
      https://lore.kernel.org/linux-cve-announce/2026072525-CVE-2026-64381-5b4a@gregkh/T
tags:
  - nvd
  - csaf
  - vex
  - red-hat
  - score-dispute
epss: 0.00129
epssPercentile: 0.02104
ingestedAt: '2026-09-08T15:33:26.949Z'
scores:
  nvd: 7.8
  vendor: 5.5
---

## Overview

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

- `linux_kernel >= 4.19, < 5.10.261`
- `linux_kernel >= 5.11, < 5.15.212`
- `linux_kernel >= 5.16, < 6.1.178`
- `linux_kernel >= 6.2, < 6.6.145`
- `linux_kernel >= 6.7, < 6.12.96`
- `linux_kernel >= 6.13, < 6.18.39`
- `linux_kernel >= 6.19, < 7.1.4`

## Remediation

Upgrade past the affected range:

- `linux_kernel 7.1.4`

## Vendor advisories

- **Red Hat VEX** · Moderate · affected: Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9 · no fix planned: Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9 · updated 2026-09-08 · [vex](https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-64381.json)