Skip to main content
VulnerabilityPublished Updated

CVE-2026-89633: Linux kernel · smb: client: fix OOB read/write from unvalidated DataOffset in coalesce_t2()

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · fixed in 6343c1da561962688f203362d80d6a3bfa39fa1b : patch Linux kernel as a priority.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 6343c1da561962688f203362d80d6a3bfa39fa1b, 672cf86aa6aa0fb4012ce4c3b3498df42ad67a4e, 36d01415d881d5326a0dd3384f781cd7e69aff2d +2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ e4eb295d38b57f4d4b956942a48887eb252d97c6, < 6343c1da561962688f203362d80d6a3bfa39fa1b
Fixed in
  • 6343c1da561962688f203362d80d6a3bfa39fa1b
LinuxLinuxAffected
  • ≥ e4eb295d38b57f4d4b956942a48887eb252d97c6, < 672cf86aa6aa0fb4012ce4c3b3498df42ad67a4e
Fixed in
  • 672cf86aa6aa0fb4012ce4c3b3498df42ad67a4e
LinuxLinuxAffected
  • ≥ e4eb295d38b57f4d4b956942a48887eb252d97c6, < 36d01415d881d5326a0dd3384f781cd7e69aff2d
Fixed in
  • 36d01415d881d5326a0dd3384f781cd7e69aff2d
LinuxLinuxAffected
  • ≥ e4eb295d38b57f4d4b956942a48887eb252d97c6, < 033bc80019f07d158630df4e69b19a49010f54f1
Fixed in
  • 033bc80019f07d158630df4e69b19a49010f54f1
LinuxLinuxAffected
  • ≥ e4eb295d38b57f4d4b956942a48887eb252d97c6, < 6eb70b78e48b0031bd1a05fe1b58959a48e87739
Fixed in
  • 6eb70b78e48b0031bd1a05fe1b58959a48e87739
LinuxLinuxAffected
  • =2.6.12
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: smb: client: fix OOB read/write from unvalidated DataOffset in coalesce_t2() coalesce_t2() computes data pointers directly from server-supplied DataOffset fields with no validation against buffer bounds: data_area_of_tgt = (char *)&pSMBt->hdr.Protocol + get_unaligned_le16(&pSMBt->t2_rsp.DataOffset); data_area_of_src = (char *)&pSMBs->hdr.Protocol + get_unaligned_le16(&pSMBs->t2_rsp.DataOffset); data_area_of_tgt += total_in_tgt; ... memcpy(data_area_of_tgt, data_area_of_src, total_in_src); A small DataOffset can push a pointer below the actual byte area, overwriting header fields; a large one can push it past the buffer end, causing out-of-bounds heap reads (source) or writes (target). The BCC overflow guard does not prevent this: BCC reflects how much data is present, while DataOffset controls where in the buffer it starts. The "validate target area" comment present since the function was first written in 2005 was a placeholder that was never implemented. Add lower- and upper-bound checks for both data pointers before the memcpy, and before any target header fields are modified.

References

Community reviews

Loading reviews…