Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-64383smb: client: fix double-free in SMB2_flush() replay

Description

In the Linux kernel, the following vulnerability has been resolved: smb: client: fix double-free in SMB2_flush() replay SMB2_flush() keeps its response buffer bookkeeping across replay attempts. If a replayable flush response is received and the retry then fails before cifs_send_recv() stores a replacement response, flush_exit will free the stale response pointer a second time. Reinitialize resp_buftype and rsp_iov at the top of the replay loop so cleanup only acts on response state produced by the current attempt. This fixes a double-free without changing replay handling for successful requests.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-64383, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.46% · top 60% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.

Affected products

  • Linux · Linux

    • affected 433042a91f9373241307725b52de573933ffedbf – < 6e27f40b682a5e42a2daae3ce6d96f0e0e16dedb
    • affected 4f1fffa2376922f3d1d506e49c0fd445b023a28e – < 878757163eea684750107a31ea134c103863515d
    • affected 4f1fffa2376922f3d1d506e49c0fd445b023a28e – < 3407240cde132a4b72d6429a2625a09a2f78adaf
    • affected 4f1fffa2376922f3d1d506e49c0fd445b023a28e – < 013a9a3da46c5dabcf18f65ea6a47874ba12a15d
    • affected 4f1fffa2376922f3d1d506e49c0fd445b023a28e – < 4be31c943a3a27a5a0251dbb8f5cb89059ec3d5a
    • affected 6.6.32 – < 6.6.145
  • Linux · Linux

    • affected 6.8
    • unaffected < 6.8
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.96 – ≤ 6.12.*
    • unaffected 6.18.39 – ≤ 6.18.*
    • unaffected 7.1.4 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64383 badge
[![CVE-2026-64383](https://cveledger.app/badge/CVE-2026-64383.svg)](https://cveledger.app/cve/CVE-2026-64383)

Record last updated .