LiveActive security incident?Get immediate response
CVE Record

CVE-2026-31608: smb: server: avoid double-free in smb_direct_free_sendmsg after smb_direct_flush_send_list()

In the Linux kernel, the following vulnerability has been resolved: smb: server: avoid double-free in smb_direct_free_sendmsg after smb_direct_flush_send_list() smb_direct_flush_send_list() already calls smb_direct_free_sendmsg(), so we should not call it again after post_sendmsg() moved it to the batch list.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A flaw in the Linux kernel’s SMB server can free the same memory twice while processing an SMB Direct send operation. This can corrupt kernel memory and potentially disrupt or compromise an affected system. The supplied CVSS score is 9.8, but the sources do not establish real-world exploitation or a specific exploitation outcome.

Executive priority

Prioritize rapid exposure assessment and vendor-supported patching for network-accessible Linux SMB servers. Escalate internet-facing or broadly reachable systems first. The rating is critical, but management should not describe this as actively exploited without new evidence. Systems not running the affected code path may have substantially lower immediate exposure.

Technical view

The flaw occurs because smb_direct_flush_send_list() calls smb_direct_free_sendmsg(), followed by another free after post_sendmsg() moves the message to the batch list. The kernel fix removes the duplicate free. The supplied assessment indicates network reachability, low complexity, no privileges, and high confidentiality, integrity, and availability impact, but does not prove code execution.

Likely exposure

Systems using affected Linux kernel builds and the SMB server’s SMB Direct send path are the primary concern. The bundle marks 6.18.24, 6.19.14, 7.0, 7.0.1, and 7.1 as affected, but also contains opaque version entries. Distribution backports may alter exposure, so package-level vendor confirmation is necessary.

Exploitation context

The CVSS vector describes a network-accessible, low-complexity issue requiring neither privileges nor user interaction. However, the bundle does not identify a public exploit, observed attacks, or CISA KEV listing. Treat exploitation as plausible based on severity, not confirmed. Exact triggering conditions and reliable impact beyond double-free memory corruption are not documented here.

Researcher notes

The source bundle provides a concise root cause and four stable-kernel fix references, but no CWE, proof of concept, attack telemetry, configuration prerequisites, or demonstrated primitive. Version data includes duplicate and opaque entries, so commit ancestry and distribution backports are more reliable than version-string comparison alone. Avoid inferring remote code execution from CVSS impacts.

Mitigation direction

  • Update to a vendor-supported kernel containing the referenced stable fix.
  • Confirm distribution backport status instead of relying only on the displayed kernel version.
  • Restrict SMB server access to trusted networks while remediation is pending.
  • Review vendor guidance before disabling SMB Direct or other production functionality.

Validation and detection

  • Inventory kernel package versions on systems providing SMB services.
  • Determine whether the SMB server and SMB Direct functionality are enabled and reachable.
  • Verify the installed kernel contains an applicable referenced fix commit or vendor backport.
  • Review kernel and SMB service logs for crashes or memory-corruption symptoms.
  • Retest service operation after updating the kernel.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-31608 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-31608Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux5ef18a2e66f2f33fdac64437bddfb9fe6389fdc7, 79242e7b6bc63efec28b7c235bc320806afce6c0, 34abd408c8ba24d7c97bd02ba874d8c714f49db1, 34abd408c8ba24d7c97bd02ba874d8c714f49db1, 6.18.11, 6.19.1unaffected
LinuxLinux7.0, 0, 6.18.24, 6.19.14, 7.0.1, 7.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.