PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-64382 Linux CVE debrief

A double-free vulnerability in the Linux kernel's SMB2_open() replay functionality has been addressed. The vulnerability occurs when a response-bearing attempt returns a replayable error and frees its response buffer. If SMB2_open_init() fails before the next send, cleanup retains the previous buffer type and frees that response again. This issue has been resolved by resetting response bookkeeping before each attempt to prevent the stale free.

Vendor
Linux
Product
Unknown
CVSS
HIGH 8.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-07-25
Original CVE updated
2026-10-19
Advisory published
2026-07-25
Advisory updated
2026-10-19

Who should care

Linux system administrators, security teams, and developers responsible for maintaining and securing Linux-based systems should be aware of this vulnerability and take necessary actions to prevent potential double-free errors.

Why it matters

The double-free vulnerability in the Linux kernel's SMB2_open() replay functionality can lead to potential security issues if not addressed. Linux system administrators and security teams should prioritize verifying and applying the patch to prevent potential double-free errors.

  • Verify patch application to prevent double-free errors.
  • Review and update Linux kernel versions to ensure they are up-to-date with the latest security patches.
  • Monitor system logs for potential exploitation attempts.

Technical summary

The Linux kernel's SMB2_open() replay functionality is vulnerable to a double-free error. This occurs when a response-bearing attempt returns a replayable error and frees its response buffer. If SMB2_open_init() fails before the next send, cleanup retains the previous buffer type and frees that response again. The issue is resolved by resetting response bookkeeping before each attempt. Linux system administrators and security teams should prioritize verifying and applying the patch to prevent potential double-free errors in the SMB2_open() replay functionality. Affected product deployments should be reviewed for potential vulnerabilities, and compensating controls should be implemented where necessary.

Defensive priority

Linux system administrators and security teams should prioritize verifying and applying the patch to prevent potential double-free errors in the SMB2_open() replay functionality.

Recommended defensive actions

  • Verify and apply the patch to prevent potential double-free errors in the SMB2_open() replay functionality.
  • Review Linux kernel versions and ensure they are up-to-date with the latest security patches.
  • Monitor system logs for potential exploitation attempts.
  • Perform a thorough review of system configurations to identify potential vulnerabilities.
  • Implement additional monitoring and logging to detect potential exploitation attempts.
  • Conduct regular security audits to ensure compliance with security best practices.
  • Review and update incident response plans to address potential security incidents.

Evidence notes

The CVE record and source item provide details on the double-free vulnerability in the Linux kernel's SMB2_open() replay functionality. The official CVE Program record and NVD vulnerability detail page offer additional information.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-64382 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-64382

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-64382 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-64382

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • smb: client: fix double-free in SMB2_open() replay

    Unverified legacy reference

    URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/64xxx/CVE-2026-64382.json

    cve_program_cvelist_v5

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/02bc2896bdc3e29362d6e40d404006944a159c25

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/3196b5192f246df4272072f61a2f4a3e9967f55d

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/14498ff5ce0f272ce0ef988721413e06b7038972

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/ff2d30927bc3bf3c629f0768d2068096e64ef5ce

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/b55e182f2324bc6a604c21a47aa6c448f719a532

    Supplemental source

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.