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).
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.6.18, 6.7.6
- CVEs
- CVE-2024-26692
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 03:25 UTC · Revision 1
Source evidence
smb: Fix regression in writes when non-standard maximum write size negotiated
core-osv · Original sourcePublished 3 Apr 2024, 14:54 UTC
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).
osv:CVE-2024-26692
Kernel
Fixed versions: 6.6.18, 6.7.6
Complete source record
{
"id": "7c69d199075c9847171fa96e9793274267937115441d1041b3093ad51abf22e7",
"url": "https://osv.dev/vulnerability/CVE-2024-26692",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "smb: Fix regression in writes when non-standard maximum write size negotiated",
"summary": "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).",
"evidence": "osv:CVE-2024-26692",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.6.18",
"evidence": "/affected/1/ranges"
},
{
"value": "6.7.6",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2024-26692",
"aliases": [
"CVE-2024-26692"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "d08089f649a0cfb2099c8551ac47eef0cc23fdf2"
},
{
"fixed": "4145ccff546ea868428b3e0fe6818c6261b574a9"
},
{
"fixed": "63c35afd50e28b49c5b75542045a8c42b696dab9"
},
{
"fixed": "4860abb91f3d7fbaf8147d54782149bb1fc45892"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-26692.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.3.0"
},
{
"fixed": "6.6.18"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.7.6"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-26692.json"
}
}
],
"modified": "2026-10-28T02:30:49.388663911Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/4145ccff546ea868428b3e0fe6818c6261b574a9",
"https://git.kernel.org/stable/c/4860abb91f3d7fbaf8147d54782149bb1fc45892",
"https://git.kernel.org/stable/c/63c35afd50e28b49c5b75542045a8c42b696dab9",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/26xxx/CVE-2024-26692.json",
"https://nvd.nist.gov/vuln/detail/CVE-2024-26692",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/26xxx/CVE-2024-26692.json"
}
},
"related_cves": [
{
"value": "CVE-2024-26692",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 517738,
"published_at": "2024-04-03T14:54:53.343+00:00"
}