CyberSecBulletin
CVE-2026-64597NVD status: Received

Linux: Double Free

CVE-2026-64597 is a critical-severity double free vulnerability in Linux, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 037511726228aaf165c7067ff2bfc88eaecdf1f3, 0aa97edf7c347c0f54e7e60c4740574b8120c66a, d15d83125007f673aec4323e1bbbaaffbe87ea13 as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.36% chance of exploitation within 30 days, which is low compared with other CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update Linux to 037511726228aaf165c7067ff2bfc88eaecdf1f3 or 0aa97edf7c347c0f54e7e60c4740574b8120c66a or d15d83125007f673aec4323e1bbbaaffbe87ea13 or b18ed621dbfceecea5539848cddcb9272c9a61e1, whichever matches your release line, or a later version.
  2. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux433042a91f9373241307725b52de573933ffedbf up to, but not including, 037511726228aaf165c7067ff2bfc88eaecdf1f3; 4f1fffa2376922f3d1d506e49c0fd445b023a28e up to, but not including, 0aa97edf7c347c0f54e7e60c4740574b8120c66a; 4f1fffa2376922f3d1d506e49c0fd445b023a28e up to, but not including, d15d83125007f673aec4323e1bbbaaffbe87ea13; 4f1fffa2376922f3d1d506e49c0fd445b023a28e up to, but not including, b18ed621dbfceecea5539848cddcb9272c9a61e1; 4f1fffa2376922f3d1d506e49c0fd445b023a28e up to, but not including, f96e1cdcb63ed3321142ff2fcdf784e32cda8fee; 6.6.32 up to, but not including, 6.6.145; 6.8037511726228aaf165c7067ff2bfc88eaecdf1f3, 0aa97edf7c347c0f54e7e60c4740574b8120c66a, d15d83125007f673aec4323e1bbbaaffbe87ea13, b18ed621dbfceecea5539848cddcb9272c9a61e1, f96e1cdcb63ed3321142ff2fcdf784e32cda8fee, 6.6.145

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.

Official description

In the Linux kernel, the following vulnerability has been resolved: smb: client: fix double-free in SMB2_close() replay A response-bearing attempt can return a replayable error and free its response buffer. If SMB2_close_init() fails before the next send, cleanup retains the previous buffer type and frees that response again. Reset response bookkeeping before each attempt to prevent the stale free.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Double Free

The product calls free() twice on the same memory address.

How developers prevent this class of flaw

  • Choose a language that provides automatic memory management.
  • Ensure that each allocation is freed only once. After freeing a chunk, set the pointer to NULL to ensure the pointer cannot be freed again. In complicated error conditions, be sure that clean-up routines respect the state of allocation properly. If the language is object oriented, ensure that object destructors delete each chunk of memory only once.
  • Use a static analysis tool to find double free instances.

More Double Free vulnerabilities (CWE-415)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Double Free vulnerabilities

Spotted an error? Tell us.