CVE-2026-98171

smb: client: fix next_buffer UAF and NextCommand bounds in compound PDUs

Published Oct 6, 2026 CVSS 3.1 · 8.8 High EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

smb: client: fix next_buffer UAF and NextCommand bounds in compound PDUs

Fix several related bounds checking and pointer lifecycle issues in
receive_encrypted_standard()'s handling of compound encrypted frames:

- Clear next_buffer after assigning it to server->bigbuf. A stale
next_buffer pointer can lead to a use-after-free on subsequent
error paths.
- Update pdu_length to the decrypted plaintext size (buf_size). Using
the pre-decryption length allows NextCommand to point into stale
ciphertext residue.
- Reject next_cmd values smaller than MID_HEADER_SIZE(server).
- Fix an integer overflow in the upper bound check by verifying
pdu_length - next_cmd < MID_HEADER_SIZE(server), ensuring the
trailing slice is large enough for a header.

Analysis

AI-generated

Technical impact

The Linux kernel SMB client contains a use‑after‑free and bounds checking flaw that occurs while processing compound encrypted frames. A stale buffer pointer can be freed and later accessed, and an incorrect length calculation can cause the next command pointer to reference leftover ciphertext. An integer overflow in the upper bound check can also allow a header to be read from an invalid location. These bugs enable memory corruption in the kernel context and, if an attacker can supply crafted SMB traffic, could lead to a denial of service or potentially arbitrary code execution within the kernel.

Affected Systems

All Linux kernel builds prior to incorporating the described patches are vulnerable. The issues reside in the SMB client code of the kernel; vendor and product name is the Linux kernel. Version information is not explicitly enumerated in the advisory, so any kernel containing the SMB client component before the fix is considered at risk.

Risk and Exploitability

The CVSS score of 8.8 indicates a high severity, and the presence of use‑after‑free and integer overflow in the SMB client suggests significant risk. The EPSS score of <1% indicates a very low current exploitation probability. The KEV catalog notes this vulnerability is not listed. The likely attack vector is an SMB client connection that processes compound encrypted frames; this inference is drawn from the description and is not explicitly stated as a proven exploit method. No public exploit is referenced, and the vulnerability is not yet in CISA’s KEV catalog, but the potential impact warrants immediate patching.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the kernel patch that introduces the proposed fixes, including clearing the stale next_buffer reference, correcting the pdu_length update, and strengthening the bounds checks—refer to the commit series at the provided kernel URLs.
  • After updating the kernel, reboot the system or reload the SMB client module to ensure the fix is active and any lingering buffers are cleared.
  • If the patch cannot be applied immediately, restrict or disable SMB client traffic to block incoming SMB connections until a kernel upgrade or patch is applied.

Generated by OpenCVE AI on October 7, 2026 at 08:26 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4841-1 linux security update
Debian DLA Debian DLA DLA-4850-1 linux-6.12 security update
Debian DSA Debian DSA DSA-6568-1 linux security update
Ubuntu USN Ubuntu USN USN-9019-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9020-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9022-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9023-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9024-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9025-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9026-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9039-1 Linux kernel (Azure CVM) vulnerabilities
Ubuntu USN Ubuntu USN USN-9040-1 Linux kernel (Low Latency NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-9066-1 Linux kernel (HWE) vulnerabilities
Ubuntu USN Ubuntu USN USN-9091-1 Linux kernel (NVIDIA Tegra) vulnerabilities
Ubuntu USN Ubuntu USN USN-9160-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9167-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9168-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9169-1 Linux kernel (AWS) vulnerabilities
Ubuntu USN Ubuntu USN USN-9168-2 Linux kernel (FIPS) vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-129
CWE-416
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}

Type Values Removed Values Added
Weaknesses CWE-190
CWE-416
Type Values Removed Values Added
Weaknesses CWE-190
CWE-416
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: smb: client: fix next_buffer UAF and NextCommand bounds in compound PDUs Fix several related bounds checking and pointer lifecycle issues in receive_encrypted_standard()'s handling of compound encrypted frames: - Clear next_buffer after assigning it to server->bigbuf. A stale next_buffer pointer can lead to a use-after-free on subsequent error paths. - Update pdu_length to the decrypted plaintext size (buf_size). Using the pre-decryption length allows NextCommand to point into stale ciphertext residue. - Reject next_cmd values smaller than MID_HEADER_SIZE(server). - Fix an integer overflow in the upper bound check by verifying pdu_length - next_cmd < MID_HEADER_SIZE(server), ensuring the trailing slice is large enough for a header.
Title smb: client: fix next_buffer UAF and NextCommand bounds in compound PDUs
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 30, 2026, 12:37 PM
Reserved
Sep 25, 2026, 10:25 AM
Status
Received
Published
Oct 6, 2026, 9:17 AM
Modified
Oct 30, 2026, 1:21 PM