CVE-2026-97563
High 7.3No known exploitationFix availablesmb: client: reject out-of-bounds DataOffset in CIFSSMBRead()
Record last updated
CVSS score
High on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 9% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
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.
Patching and mitigation
- Patch status
- Fix available (source: Microsoft MSRC)
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- msrc.microsoft.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Linux | Linux | from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 667feba13e78d16393aacb15869f70970f422227 | 667feba13e78d16393aacb15869f70970f422227 | CVE Program |
| Linux | Linux | from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 5be5bdda5863eacc964b609ba927764f253431b3 | 5be5bdda5863eacc964b609ba927764f253431b3 | CVE Program |
| Linux | Linux | 2.6.12 | Not documented | CVE Program |
| Microsoft | azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Not documented | Not documented | Microsoft MSRC |
| Microsoft | azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | Not documented | Not documented | Microsoft MSRC |
| Microsoft | azl3 kernel 6.6.161.1-1 on Azure Linux 3.0 | Not documented | Not documented | Microsoft MSRC |
| Linux | Linux (unaffected) | from 7.2.7 up to and including 7.2.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | 7.3 | Not documented | CVE Program |
| Linux | Linux (unaffected) | all versions before 2.6.12 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by Linux
Source: CVE Program (opens in a new tab)
Advisory
Microsoft advisory published
Advisory change
Microsoft advisory revised (2.0): Information published.
Advisory change
Microsoft advisory revised (3.0): Information published.
Advisory change
Microsoft advisory revised (4.0): Information published.
Patch
Fix documented by Microsoft MSRC