Kernel memory corruption via stale SMB response double-free
Published Jul 25, 2026 · Updated Jul 25, 2026
Double-free in the Linux Kernel SMB client allows remote attackers to corrupt kernel memory through replayed change-notify responses. SMB2_change_notify frees a response buffer after a replayable error, while SMB2_notify_init failure leaves its stale response type for cleanup to free again. An SMB client must connect to a malicious server that controls the replay and reconnection failure; allocator behavior determines whether corruption causes a panic, later crash, memory disclosure, or attacker-influenced kernel writes.
Summary
What happened
Double-free in the Linux Kernel SMB client allows remote attackers to corrupt kernel memory through replayed change-notify responses. SMB2_change_notify frees a response buffer after a replayable error, while SMB2_notify_init failure leaves its stale response type for cleanup to free again. An SMB client must connect to a malicious server that controls the replay and reconnection failure; allocator behavior determines whether corruption causes a panic, later crash, memory disclosure, or attacker-influenced kernel writes.
The record
- CVE
- CVE-2026-64384
- Published
- Jul 25, 2026
- Updated
- Jul 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 25, 2026CVE publishedPublication date reported by the CVE source.
- Jul 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=433042a91f9373241307725b52de573933ffedbf <5821f9dbb8b5b24391850a13418e633edd0fb003
- Affected versionversion=4f1fffa2376922f3d1d506e49c0fd445b023a28e <145f820dcbb2cced374f2532f8a61a44dce4a615
- Affected versionversion=4f1fffa2376922f3d1d506e49c0fd445b023a28e <52af1975f0dfae990c5a0e85872cc41be0e88a68
- Affected versionversion=4f1fffa2376922f3d1d506e49c0fd445b023a28e <901891513951bc8322ece754863909ea45af95c6
- Affected versionversion=4f1fffa2376922f3d1d506e49c0fd445b023a28e <d684f4134998085702009b94c35c2003fc9e72d3
- Affected versionversion=6.6.32 <6.6.145
- Affected versionversion=6.8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo