In the Linux kernel, the following vulnerability has been resolved: smb: client: fix double-free in SMB2_close() replay A response-bearing attempt… (CVE-2026-64597)
A double-free vulnerability in the Linux kernel SMB client was resolved. The flaw occurs in the SMB2_close() function where a response buffer may be freed twice due to improper bookkeeping when handling replayable errors. This can lead to memory corruption. The fix involves resetting response bookkeeping before each attempt to prevent freeing stale buffers.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel SMB client involves a double-free condition in the SMB2_close() function. When a response-bearing attempt returns a replayable error and frees its response buffer, a subsequent failure in SMB2_close_init() before the next send causes cleanup to incorrectly free the same response buffer again. This improper handling of response buffers can lead to memory corruption. The issue was fixed by resetting response bookkeeping before each attempt to avoid freeing stale buffers multiple times.
Potential Impact
The vulnerability can cause memory corruption in the Linux kernel SMB client due to a double-free condition. This may lead to system instability or potential exploitation depending on the context in which the kernel is used. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel. Users should apply the official kernel updates that include this patch. Since no vendor advisory or patch links are provided, check the Linux kernel mailing lists or official repositories for the relevant patch. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix double-free in SMB2_close() replay A response-bearing attempt… (CVE-2026-64597)
Description
A double-free vulnerability in the Linux kernel SMB client was resolved. The flaw occurs in the SMB2_close() function where a response buffer may be freed twice due to improper bookkeeping when handling replayable errors. This can lead to memory corruption. The fix involves resetting response bookkeeping before each attempt to prevent freeing stale buffers.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel SMB client involves a double-free condition in the SMB2_close() function. When a response-bearing attempt returns a replayable error and frees its response buffer, a subsequent failure in SMB2_close_init() before the next send causes cleanup to incorrectly free the same response buffer again. This improper handling of response buffers can lead to memory corruption. The issue was fixed by resetting response bookkeeping before each attempt to avoid freeing stale buffers multiple times.
Potential Impact
The vulnerability can cause memory corruption in the Linux kernel SMB client due to a double-free condition. This may lead to system instability or potential exploitation depending on the context in which the kernel is used. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel. Users should apply the official kernel updates that include this patch. Since no vendor advisory or patch links are provided, check the Linux kernel mailing lists or official repositories for the relevant patch. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-4vgx-hp6g-jmm8
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64597"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a74cfa0bf8831d5391b0790
Added to database: 08/06/2026, 18:17:04 UTC
Last enriched: 08/06/2026, 19:12:21 UTC
Last updated: 08/07/2026, 00:41:15 UTC
Views: 2
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.