In the Linux kernel, the following vulnerability has been resolved: smb: client: fix double-free in SMB2_open() replay A response-bearing attempt… (CVE-2026-64382)
A double-free vulnerability in the Linux kernel's SMB client implementation (SMB2_open) has been resolved. The issue occurs when a response-bearing attempt returns a replayable error and frees its response buffer, but a subsequent failure in SMB2_open_init() causes the previous buffer to be freed again due to stale bookkeeping. This can lead to memory corruption. The fix involves resetting response bookkeeping before each attempt to prevent double-free errors.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel SMB client involves a double-free condition in the SMB2_open() function. When a response-bearing attempt returns a replayable error, it frees its response buffer. If SMB2_open_init() fails before the next send, the cleanup process mistakenly frees the previously freed response buffer again because it retains stale buffer type information. The patch resets the response bookkeeping before each attempt to avoid this double-free scenario.
Potential Impact
The double-free vulnerability can cause memory corruption in the Linux kernel SMB client code. This may lead to system instability or potential denial of service. No known exploits in the wild have been reported. The exact impact beyond memory corruption is not detailed in the provided information.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel. Since no patch links or vendor advisories are provided, users should monitor official Linux kernel releases and apply updates that address CVE-2026-64382. 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_open() replay A response-bearing attempt… (CVE-2026-64382)
Description
A double-free vulnerability in the Linux kernel's SMB client implementation (SMB2_open) has been resolved. The issue occurs when a response-bearing attempt returns a replayable error and frees its response buffer, but a subsequent failure in SMB2_open_init() causes the previous buffer to be freed again due to stale bookkeeping. This can lead to memory corruption. The fix involves resetting response bookkeeping before each attempt to prevent double-free errors.
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_open() function. When a response-bearing attempt returns a replayable error, it frees its response buffer. If SMB2_open_init() fails before the next send, the cleanup process mistakenly frees the previously freed response buffer again because it retains stale buffer type information. The patch resets the response bookkeeping before each attempt to avoid this double-free scenario.
Potential Impact
The double-free vulnerability can cause memory corruption in the Linux kernel SMB client code. This may lead to system instability or potential denial of service. No known exploits in the wild have been reported. The exact impact beyond memory corruption is not detailed in the provided information.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel. Since no patch links or vendor advisories are provided, users should monitor official Linux kernel releases and apply updates that address CVE-2026-64382. Patch status is not yet confirmed—check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-9v59-2cj8-p55r
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64382"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a65420b9c2644c7f8084a30
Added to database: 07/25/2026, 23:08:59 UTC
Last enriched: 07/25/2026, 23:29:28 UTC
Last updated: 07/26/2026, 03:54:54 UTC
Views: 4
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.