In the Linux kernel, the following vulnerability has been resolved: smb: client: reject out-of-bounds DataOffset in CIFSSMBRead() The SMB1 synchronous read helper CIFSSMBRead() validates the server's DataLength against CIFSMaxBufSize and the caller's count, but never validates DataOffset. The copy source is formed as &pSMBr->hdr.Protocol + le16_to_cpu(pSMBr->DataOffset) and memcpy()'d for DataLength bytes with no check that the [DataOffset, DataOffset + DataLength) range lies within the response actually received from the server. A malicious or compromised SMB1 server can return a response carrying an in-range DataLength and a large DataOffset, driving the source pointer past the end of the response buffer. The memcpy() then copies adjacent kernel heap into the caller's read buffer (information disclosure), or reads unmapped memory and oopses (denial of service). SMB1 is not negotiated by default; reaching this code requires an explicit vers=1.0 mount. Both DataOffset and the received response length recorded in rsp_iov.iov_len are relative to the start of the SMB header, so reject the response unless DataOffset + DataLength fits within that length, using overflow-safe arithmetic, before forming the source pointer. The response length has been validated by the previous patch, so the DataOffset and DataLength fields can be read safely here. While here, make data_length unsigned. It holds a length derived from unsigned on-the-wire fields and is only ever compared against unsigned quantities; print it with %u accordingly, and add __func__ to the cifs_dbg() calls in this function.
Fix
STIG rules that mitigate this class
A system with the SMBv1 server and client disabled does not speak the protocol the flaw is in. Microsoft Learn, "Detect, enable and disable SMBv1, SMBv2, and SMBv3 in Windows" (the owner's mapping, data/mitigations.yaml: smbv1)
- WN11-00-000160 CAT II The Server Message Block (SMB) v1 protocol must be disabled on the system. Microsoft Windows 11
- WN11-00-000165 CAT II The Server Message Block (SMB) v1 protocol must be disabled on the SMB server. Microsoft Windows 11
- WN11-00-000170 CAT II The Server Message Block (SMB) v1 protocol must be disabled on the SMB client. Microsoft Windows 11
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 2
- StatusReceived → PublishedNVD modified 2026-10-19 09:09
- First seenunscoredNVD modified 2026-10-19 10:17
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.