Skip to content
Noroxi
CVE-2026-89633· NVD / CVE Program· CNA Linux

smb: client: fix OOB read/write from unvalidated DataOffset in coalesce_t2()

Noroxi assessment

Priority: Monitor (action score 39/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.49% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 033bc80019f07d158630df4e69b19a49010f54f1, 36d01415d881d5326a0dd3384f781cd7e69aff2d, 6343c1da561962688f203362d80d6a3bfa39fa1b.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 033bc80019f07d158630df4e69b19a49010f54f1, 36d01415d881d5326a0dd3384f781cd7e69aff2d, 6343c1da561962688f203362d80d6a3bfa39fa1b or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

CriticalCVSS 9.8 · v3.1—No exploit Fix available
Published
Sep 11, 2026
Updated
Oct 21, 2026
EPSS
0.4% · 41th percentile
CWE
—

Report tools

JSON

Action score

39

Monitor

Low priority for now.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CNA vs NVD score

NVD
—
CNA · Linux
9.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-89633

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.12affected
    • e4eb295d38b57f4d4b956942a48887eb252d97c6 and later · before 6eb70b78e48b0031bd1a05fe1b58959a48e87739affected · git
    • e4eb295d38b57f4d4b956942a48887eb252d97c6 and later · before 36d01415d881d5326a0dd3384f781cd7e69aff2daffected · git
    • e4eb295d38b57f4d4b956942a48887eb252d97c6 and later · before 672cf86aa6aa0fb4012ce4c3b3498df42ad67a4eaffected · git
    • e4eb295d38b57f4d4b956942a48887eb252d97c6 and later · before 033bc80019f07d158630df4e69b19a49010f54f1affected · git
    • e4eb295d38b57f4d4b956942a48887eb252d97c6 and later · before 6343c1da561962688f203362d80d6a3bfa39fa1baffected · git
    • before 2.6.12not affected · semver
    • 6.6.160 and later · up to and including 6.6.*not affected · semver
    • 6.12.113 and later · up to and including 6.12.*not affected · semver
    • 6.18.51 and later · up to and including 6.18.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-89631Sep 11, 2026 · smb: client: reject a tree connect response whose byte count is too small
    36Monitor
  • ← EarlierCVE-2026-89632Sep 11, 2026 · smb: client: fix use-before-check of ReparseDataLength in reparse_buf_ptr()
    32Monitor
  • Later →CVE-2026-89634Sep 11, 2026 · smb: client: fix ALIGN() overflow in symlink_data() error context loop
    36Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux033bc80019f07d158630df4e69b19a49010f54f1Vendor (CNA)
Linux Linux36d01415d881d5326a0dd3384f781cd7e69aff2dVendor (CNA)
Linux Linux6343c1da561962688f203362d80d6a3bfa39fa1bVendor (CNA)
Linux Linux672cf86aa6aa0fb4012ce4c3b3498df42ad67a4eVendor (CNA)
Linux Linux6eb70b78e48b0031bd1a05fe1b58959a48e87739Vendor (CNA)
almalinux:kernel6.12.0-211.67.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-211.67.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.67.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.67.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.67.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.67.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.67.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.67.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.67.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.67.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.67.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.67.1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:linux6.12.113-1 · Debian:13Package registry (OSV)
debian:linux7.2.6-1 · Debian:14Package registry (OSV)
debian:linux-6.126.12.113-1~deb12u1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-211.67.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-211.67.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-211.67.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-211.67.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-211.67.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-211.67.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-211.67.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-211.67.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-211.67.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo0:6.12.0-211.67.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)

+3

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records