Answer in brief
CVE-2024-26692 records a Unknown severity vulnerability in smb: Fix regression in writes when non-standard maximum write size negotiated. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d08089f649a0cfb2099c8551ac47eef0cc23fdf2 <4145ccff546ea868428b3e0fe6818c6261b574a9 || >=d08089f649a0cfb2099c8551ac47eef0cc23fdf2 <63c35afd50e28b49c5b75542045a8c42b696dab9 || >=d08089f649a0cfb2099c8551ac47eef0cc23fdf2 <4860abb91f3d7fbaf8147d54782149bb1fc45892 | 4145ccff546ea868428b3e0fe6818c6261b574a9, 63c35afd50e28b49c5b75542045a8c42b696dab9, 4860abb91f3d7fbaf8147d54782149bb1fc45892 |
| Linux/Linuxgeneric | 6.3 | Not reported |
Published upstream
Apr 3, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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).
Quoted source text, attributed separately from HOL analysis.