CVE-2025-39943 in the critical feed json
ksmbd: smbdirect: validate data_offset and data_length field of smb_direct_data_transfer
published last yr. modified 21d ago also EUVD-2025-32382
- cvss
- 9.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 18%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: smbdirect: validate data_offset and data_length field of smb_direct_data_transfer
If data_offset and data_length of smb_direct_data_transfer struct are invalid, out of bounds issue could happen. This patch validate data_offset and data_length field in recv_done.
Patch / fix
- Linux Linux 5.15.194, 6.1.154, 6.6.108, 6.12.49, 6.16.9, 6.17
- linux Debian 12 6.1.158-1
- linux Debian 13 6.12.57-1
- linux Debian 14 6.16.9-1
debian advisories DEBIAN-CVE-2025-39943
- linux Ubuntu 22.04 LTS 5.15.0-170.180
- linux Ubuntu 24.04 LTS 6.8.0-106.106
- linux-aws Ubuntu 22.04 LTS 5.15.0-1100.107
- linux-aws Ubuntu 24.04 LTS 6.8.0-1050.53
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1100.109
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1052.55
- linux-gke Ubuntu 22.04 LTS 5.15.0-1096.102
- linux-gke Ubuntu 24.04 LTS 6.8.0-1048.53
ubuntu advisories UBUNTU-CVE-2025-39943
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
- git.kernel.org/stable/c/773fddf976d282ef059c36c575ddb81567acd6bc commit
- git.kernel.org/stable/c/bdaab5c6538e250a9654127e688ecbbeb6f771d5 commit
- git.kernel.org/stable/c/eb0378dde086363046ed3d7db7f126fc3f76fd70 commit
- git.kernel.org/stable/c/8be498fcbd5b07272f560b45981d4b9e5a2ad885 commit
- git.kernel.org/stable/c/529b121b00a6ee3c88fb3c01b443b2b81f686d48 commit
- git.kernel.org/stable/c/5282491fc49d5614ac6ddcd012e5743eecb6a67c commit
Is CVE-2025-39943 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 FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-39943 updated
kernel: ksmbd: smbdirect: validate data_offset and data_length field of smb_direct_data_transfer
-
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.26% chance of exploitation in the next 30 days, higher than 18% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.4 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H |
| 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
-
- CWE-125 Out-of-bounds Read
- Technology feeds
References
-
git.kernel.org
/stable/c/773fddf976d282ef059c36c575ddb81567acd6bc
patch
-
git.kernel.org
/stable/c/bdaab5c6538e250a9654127e688ecbbeb6f771d5
patch
-
git.kernel.org
/stable/c/eb0378dde086363046ed3d7db7f126fc3f76fd70
patch
-
git.kernel.org
/stable/c/8be498fcbd5b07272f560b45981d4b9e5a2ad885
patch
-
git.kernel.org
/stable/c/529b121b00a6ee3c88fb3c01b443b2b81f686d48
patch
-
git.kernel.org
/stable/c/5282491fc49d5614ac6ddcd012e5743eecb6a67c
patch
Sources
- CVE List CVE-2025-39943
- NVD CVE-2025-39943
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.