Skip to main content
CVE-2026-64381VulnerabilityPublished 07/25/2026

In the Linux kernel, the following vulnerability has been resolved: smb: client: Fix next buffer leak in receive_encrypted_standard()… (CVE-2026-64381)

Source GCVE Database

0

Not known to be exploited : monitor for a fix to affected systems.

Data as of 10/24/2026, 20:40:31 UTC

Severity
Low

No CVSS score from NVD or the CNA

Exploitation

Not in CISA KEV, no exploitation reported

EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

What to do

AI-suggested

The vulnerability has been resolved in the Linux kernel by reordering the check and allocation in the receive_encrypted_standard() function. No specific patch links are provided here; users should apply the latest Linux kernel updates from their vendor or distribution to receive this fix.

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.

Impact

This vulnerability causes a memory leak in the Linux kernel SMB client. While it does not directly lead to code execution or privilege escalation, memory leaks can degrade system performance or stability over time. There are no known exploits in the wild for this issue.

References

Community reviews

Loading reviews…