LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26692: smb: Fix regression in writes when non-standard maximum write size negotiated

In the Linux kernel, the following vulnerability has been resolved: smb: Fix regression in writes when non-standard maximum write size negotiated The conversion to netfs in the 6.3 kernel caused a regression when maximum write size is set by the server to an unexpected value which is not a multiple of 4096 (similarly if the user overrides the maximum write size by setting mount parm "wsize", but sets it to a value that is not a multiple of 4096). When negotiated write size is not a multiple of 4096 the netfs code can skip the end of the final page when doing large sequential writes, causing data corruption. This section of code is being rewritten/removed due to a large netfs change, but until that point (ie for the 6.3 kernel until now) we can not support non-standard maximum write sizes. Add a warning if a user specifies a wsize on mount that is not a multiple of 4096 (and round down), also add a change where we round down the maximum write size if the server negotiates a value that is not a multiple of 4096 (we also have to check to make sure that we do not round it down to zero).

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-26692 is a Linux kernel SMB client issue that can corrupt data during large sequential writes. It occurs when the SMB server or mount option uses a maximum write size that is not a multiple of 4096. This is an integrity risk, not a reported code-execution issue.

Executive priority

Treat as a data integrity issue for Linux systems writing to SMB shares. Prioritize file servers, backup workflows, data pipelines, and business processes where silent corruption would be costly.

Technical view

A netfs conversion regression introduced around Linux 6.3 affected SMB write handling. If negotiated or user-specified maximum write size is not 4096-aligned, netfs may skip the end of the final page during large writes. Kernel fixes round down non-standard sizes and warn on invalid mount wsize values.

Likely exposure

Exposure is most likely on Linux systems using SMB/CIFS mounts for writes, especially kernels in the affected 6.3-era range and environments with non-standard SMB maximum write sizes or custom wsize mount settings.

Exploitation context

No active exploitation is reported in the provided sources, and the CVE is not listed as KEV. Practical impact appears to require SMB client write activity under specific negotiated or configured write-size conditions.

Researcher notes

The available record describes a regression and fix behavior but provides no CVSS, CWE, exploit evidence, or distribution-specific advisory details. The key condition is a non-4096-multiple maximum write size negotiated by the server or set via mount wsize.

Mitigation direction

  • Update Linux kernels using vendor guidance or stable kernel fixes referenced for this CVE.
  • Check SMB/CIFS mount options for wsize values not divisible by 4096.
  • Avoid non-standard SMB maximum write sizes until systems are patched.
  • Prioritize backups and integrity checks for data written through affected SMB mounts.

Validation and detection

  • Inventory Linux kernels on systems using SMB/CIFS mounts.
  • Identify SMB/CIFS mounts performing write-heavy or large sequential write workloads.
  • Review mount configurations for custom wsize values not divisible by 4096.
  • Check vendor advisories to confirm the fixed kernel package is installed.
  • Validate critical files written over SMB using application-level integrity checks.
Prepared
Confidence
high
Sources
5

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-2024-26692 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd08089f649a0cfb2099c8551ac47eef0cc23fdf2, d08089f649a0cfb2099c8551ac47eef0cc23fdf2, d08089f649a0cfb2099c8551ac47eef0cc23fdf2unaffected
LinuxLinux6.3, 0, 6.6.18, 6.7.6, 6.8affected
Weakness

CWE details

No CWE listed

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