Menu

Star on GitHub · 3.2k

CVE-2026-64381

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 che…

Published Jul 25, 2026EPSS 0.13%

Overview

CVE-2026-64381 is a known-severity vulnerability. It was published on July 25, 2026.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-64381?

CVE-2026-64381 is a known-severity vulnerability. It was published on July 25, 2026.

How severe is CVE-2026-64381?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-64381?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-64381?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-64381 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.