Security readout for executives and security teams
Plain-English summary
A Linux SMB client bug can corrupt kernel memory when encrypted multichannel file-sharing traffic is decrypted concurrently. Affected systems could crash, and the published score rates potential impact as critical. Exposure appears configuration-dependent. The supplied sources contain no evidence of active exploitation, so urgency should focus on locating encrypted multichannel SMB clients and applying vendor-confirmed kernel fixes.
Executive priority
Prioritize exposure verification within 24 hours for Linux systems using encrypted SMB multichannel connections. Expedite vendor-approved kernel updates for confirmed matches. Systems without that configuration have lower demonstrated urgency, although normal kernel maintenance remains appropriate.
Technical view
The CIFS client reused the primary channel's AEAD crypto transform across per-channel cifsd threads. Concurrent synchronous decryption can race over shared crypto state, causing a slab use-after-free in the GHASH/GCM path. KASAN reproduced an invalid read. The evidence establishes a memory-safety failure but does not demonstrate practical code execution or data compromise.
Likely exposure
Most likely exposure is Linux systems acting as SMB clients with multichannel and encryption enabled concurrently. The documented reproduction used SMB 3.1.1, four channels, sealing, and Windows Server 2022. The supplied evidence does not establish exposure for systems outside this configuration pattern.
Exploitation context
CISA KEV status is false, and no supplied source reports active exploitation. The evidence is a KASAN-detected failure during filesystem testing. It does not demonstrate reliable attacker control, code execution, or exploitation in production. The 9.8 CVSS score represents assessed potential impact, not proof of exploitation.
Researcher notes
The supplied affected-version data is ambiguous, including broad releases, specific versions, duplicate commits, and an entry of "0." Four stable fix commits are cited without explicit branch mapping. Validate applicability through the relevant distribution or kernel vendor. Treat confidentiality and integrity impact as scored potential, because the reproduction only establishes an invalid kernel-memory read.
Mitigation direction
- Apply the distribution or kernel vendor update incorporating the applicable cited stable fix.
- Until patched, consider disabling SMB multichannel for encrypted mounts after testing operational impact.
- Restrict SMB client access to trusted servers and networks as defense in depth.
- Check vendor guidance before changing encryption or production mount settings.
Validation and detection
- Inventory Linux systems using the CIFS or SMB client and record running kernel versions.
- Identify mounts using SMB 3.1.1, multichannel, multiple channels, and encryption.
- Confirm vendor kernel packages contain the applicable cited stable-kernel fix.
- Review kernel logs for CIFS crashes, KASAN reports, or use-after-free signatures.
- Regression-test encrypted multichannel mounts after updating, including concurrent traffic across channels.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2025-37750 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9LinuxVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/aa5a1e4b882964eb79d5b5d1d1e8a1a5efbb1d15CVE reference, Linux
- https://git.kernel.org/stable/c/e859b216d94668bc66330e61be201234f4413d1aCVE reference, Linux
- https://git.kernel.org/stable/c/950557922c1298464749c216d8763e97faf5d0a6CVE reference, Linux
- https://git.kernel.org/stable/c/9502dd5c7029902f4a425bf959917a5a9e7c0e50CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.