Skip to content
Threat Brief

← All advisories

CVE-2026-97563

High 7.3No known exploitationFix available

smb: client: reject out-of-bounds DataOffset in CIFSSMBRead()

Record last updated

CVSS score

7.3

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.2%

Higher than 9% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

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

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 667feba13e78d16393aacb15869f70970f422227667feba13e78d16393aacb15869f70970f422227CVE Program
LinuxLinuxfrom 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 5be5bdda5863eacc964b609ba927764f253431b35be5bdda5863eacc964b609ba927764f253431b3CVE Program
LinuxLinux2.6.12Not documentedCVE Program
Microsoftazl3 kernel 6.6.157.1-1 on Azure Linux 3.0Not documentedNot documentedMicrosoft MSRC
Microsoftazl3 kernel 6.6.159.1-1 on Azure Linux 3.0Not documentedNot documentedMicrosoft MSRC
Microsoftazl3 kernel 6.6.161.1-1 on Azure Linux 3.0Not documentedNot documentedMicrosoft MSRC
LinuxLinux (unaffected)from 7.2.7 up to and including 7.2.*Not documentedCVE Program
LinuxLinux (unaffected)7.3Not documentedCVE Program
LinuxLinux (unaffected)all versions before 2.6.12Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  3. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  4. Advisory change

    Microsoft advisory revised (3.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  5. Advisory change

    Microsoft advisory revised (4.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  6. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references