Skip to content
Fencer Intel
high 7.1

CVE-2026-31614 json

smb: client: fix off-by-8 bounds check in check_wsl_eas()

published 6mo ago modified 3d ago also EUVD-2026-25507

cvss
7.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 2%
public exploits
0
none known

Summary

In the Linux kernel, the following vulnerability has been resolved:

smb: client: fix off-by-8 bounds check in check_wsl_eas()

The bounds check uses (u8 *)ea + nlen + 1 + vlen as the end of the EA name and value, but ea_data sits at offset sizeof(struct smb2_file_full_ea_info) = 8 from ea, not at offset 0. The strncmp() later reads ea->ea_data[0..nlen-1] and the value bytes follow at ea_data[nlen+1..nlen+vlen], so the actual end is ea->ea_data + nlen + 1 + vlen. Isn't pointer math fun?

The earlier check (u8 *)ea > end - sizeof(*ea) only guarantees the 8-byte header is in bounds, but since the last EA is placed within 8 bytes of the end of the response, the name and value bytes are read past the end of iov.

Fix this mess all up by using ea->ea_data as the base for the bounds check.

An "untrusted" server can use this to leak up to 8 bytes of kernel heap into the EA name comparison and influence which WSL xattr the data is interpreted as.

Patch / fix

  • Linux Linux 6.6.136, 6.12.83, 6.18.24, 6.19.14, 7.0.1, 7.1
  • linux Debian 13 6.12.85-1
  • linux Debian 14 6.19.14-1

debian advisories DEBIAN-CVE-2026-31614

  • linux Ubuntu 26.04 LTS 7.0.0-27.27
  • linux-aws Ubuntu 26.04 LTS 7.0.0-1008.8
  • linux-gcp Ubuntu 26.04 LTS 7.0.0-1007.7
  • linux-ibm Ubuntu 26.04 LTS 7.0.0-1009.9
  • linux-azure Ubuntu 26.04 LTS 7.0.0-1010.10
  • linux-raspi Ubuntu 26.04 LTS 7.0.0-1014.14
  • linux-riscv Ubuntu 26.04 LTS 7.0.0-27.27.1
  • linux-nvidia Ubuntu 26.04 LTS 7.0.0-1013.13

ubuntu advisories UBUNTU-CVE-2026-31614

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-48.1
  • kernel-source-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-48.1
  • kernel-rt Real Time Module 15 SP7 6.4.0-150700.7.59.2
  • kernel-syms-rt Real Time Module 15 SP7 6.4.0-150700.7.59.1
  • kernel-source-rt Real Time Module 15 SP7 6.4.0-150700.7.59.2
  • kernel-64kb SLE Module for Basesystem 15 SP7 6.4.0-150700.53.60.1
  • kernel-syms SLE Module for Development Tools 15 SP7 6.4.0-150700.53.60.1
  • kernel-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.53.60.1

suse advisories SUSE-SU-2026:22433-1SUSE-SU-2026:22458-1SUSE-SU-2026:2591-1SUSE-SU-2026:2482-1SUSE-SU-2026:22108-1SUSE-SU-2026:22137-1

  • kernel-source openSUSE Tumbleweed 7.0.3-1.1

opensuse advisories openSUSE-SU-2026:10703-1

  • kernel Azure Linux 3.0 6.6.137.1-1

azure linux advisories AZL-83852

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2026-31614 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-31614 updated cvss 5.7

kernel: smb: client: fix off-by-8 bounds check in check_wsl_eas()

  • 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 kernel
    affected: workaround, no fix available “To mitigate this issue, prevent the cifs module from being loaded. See https://access.redhat.com/solutions/41278 for instructions.”
  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more
    not 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

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
3d ago

Exploit prediction

0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 7.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Affected products

  • Linux Linux

Classification

Weakness
Technology feeds

References

Sources

Fencer Intel 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.