In the Linux kernel, the following vulnerability has been resolved: smb: client: Fix next buffer leak in receive_encrypted_standard()… (CVE-2026-64381)
A memory leak vulnerability in the Linux kernel SMB client was resolved by correcting the order of operations in the receive_encrypted_standard() function. The function previously allocated a buffer before checking if the maximum number of compound PDUs was reached, causing a buffer leak when the limit was exceeded. The fix moves the limit check before buffer allocation to prevent this leak.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel SMB client involves a buffer leak in the receive_encrypted_standard() function. The function allocates a next_buffer before verifying if the number of compound PDUs has reached the MAX_COMPOUND limit. If the limit is exceeded, the function returns early without assigning the allocated buffer to the server's buffer pointers, resulting in a memory leak. The patch corrects this by performing the MAX_COMPOUND check prior to buffer allocation, preventing the leak.
Potential 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.
Mitigation Recommendations
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. Patch status is not yet confirmed in this data — check the vendor advisory for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: smb: client: Fix next buffer leak in receive_encrypted_standard()… (CVE-2026-64381)
Description
A memory leak vulnerability in the Linux kernel SMB client was resolved by correcting the order of operations in the receive_encrypted_standard() function. The function previously allocated a buffer before checking if the maximum number of compound PDUs was reached, causing a buffer leak when the limit was exceeded. The fix moves the limit check before buffer allocation to prevent this leak.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel SMB client involves a buffer leak in the receive_encrypted_standard() function. The function allocates a next_buffer before verifying if the number of compound PDUs has reached the MAX_COMPOUND limit. If the limit is exceeded, the function returns early without assigning the allocated buffer to the server's buffer pointers, resulting in a memory leak. The patch corrects this by performing the MAX_COMPOUND check prior to buffer allocation, preventing the leak.
Potential 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.
Mitigation Recommendations
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. Patch status is not yet confirmed in this data — check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-v5fg-wc2f-7h9h
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64381"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a65420a9c2644c7f8084460
Added to database: 07/25/2026, 23:08:58 UTC
Last enriched: 07/25/2026, 23:27:49 UTC
Last updated: 07/26/2026, 03:59:38 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.