CVE-2026-64257 in the critical feed json
smb: client: reject overlapping data areas in SMB2 responses
published 2026-07-25 3 mo ago modified 2026-08-17 2 mo ago also EUVD-2026-48969
- cvss
- 9.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 51%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
smb: client: reject overlapping data areas in SMB2 responses
Commit 53b7c271f06b ("smb: client: restrict implied bcc[0] exemption to responses without data area") restricted the implied bcc[0] length exception to responses without a data area. However, the overlap handling in __smb2_calc_size() clears data_length, which can make an invalid response appear to have no data area and so qualify for the exception.
Track data area overlap separately and reject such responses before applying the length compatibility exceptions.
Patch / fix
- Linux Linux 5.11, 5.16
- kernel-64kb SLE Module for Basesystem 15 SP7 6.4.0-150700.53.81.1
- kernel-syms SLE Module for Development Tools 15 SP7 6.4.0-150700.53.81.1
- kernel-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.53.81.1
- kernel-source SLE Module for Development Tools 15 SP7, SLE Module for Basesystem 15 SP7 6.4.0-150700.53.81.1
- kernel-default SLE Workstation Extension 15 SP7, SLE Module for Legacy 15 SP7, SLE Module for Basesystem 15 SP7 +2 more 6.4.0-150700.53.81.1
- kernel-zfcpdump SLE Module for Basesystem 15 SP7 6.4.0-150700.53.81.1
- kernel-obs-build SLE Module for Development Tools 15 SP7 6.4.0-150700.53.81.1
- kernel-default-base SLE Module for Basesystem 15 SP7 6.4.0-150700.53.81.1.150700.17.45.1
suse advisories SUSE-SU-2026:5121-1SUSE-SU-2026:4254-1SUSE-SU-2026:4120-1SUSE-SU-2026:23481-1SUSE-SU-2026:23477-1SUSE-SU-2026:23529-1
- kernel-source openSUSE Tumbleweed 7.1.7-1.1
opensuse advisories openSUSE-SU-2026:11476-1
- git.kernel.org/stable/c/445ece263131780dee273d727a4d6f11934feec7 commit
- git.kernel.org/stable/c/36bfa52459e45c0d5b668de2f1c91f6dc5c67775 commit
- git.kernel.org/stable/c/4a9d2657d3e05f6ed09c148cb127b4e58702275f commit
- git.kernel.org/stable/c/fdafa1e68dc75045b7b617e6e7d2854950804d83 commit
- git.kernel.org/stable/c/57cba95f0e97c6f6e45e6731da30aff091bd7460 commit
- git.kernel.org/stable/c/8986c932905ea508d66da421eb2eb6e676ace1fe commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-64257 updated
kernel: smb: client: reject overlapping data areas in SMB2 responses
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.66% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/445ece263131780dee273d727a4d6f11934feec7
patch
-
git.kernel.org
/stable/c/36bfa52459e45c0d5b668de2f1c91f6dc5c67775
patch
-
git.kernel.org
/stable/c/4a9d2657d3e05f6ed09c148cb127b4e58702275f
patch
-
git.kernel.org
/stable/c/fdafa1e68dc75045b7b617e6e7d2854950804d83
patch
-
git.kernel.org
/stable/c/57cba95f0e97c6f6e45e6731da30aff091bd7460
patch
-
git.kernel.org
/stable/c/8986c932905ea508d66da421eb2eb6e676ace1fe
patch
Sources
- CVE List CVE-2026-64257
- NVD CVE-2026-64257
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.