CVE-2026-31717 json
ksmbd: validate owner of durable handle on reconnect
published 2026-05-01 6 mo ago modified 2026-08-05 3 mo ago also EUVD-2026-26526
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 38%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: validate owner of durable handle on reconnect
Currently, ksmbd does not verify if the user attempting to reconnect to a durable handle is the same user who originally opened the file. This allows any authenticated user to hijack an orphaned durable handle by predicting or brute-forcing the persistent ID.
According to MS-SMB2, the server MUST verify that the SecurityContext of the reconnect request matches the SecurityContext associated with the existing open. Add a durable_owner structure to ksmbd_file to store the original opener's UID, GID, and account name. and catpure the owner information when a file handle becomes orphaned. and implementing ksmbd_vfs_compare_durable_owner() to validate the identity of the requester during SMB2_CREATE (DHnC).
Patch / fix
- Linux Linux 6.6.142, 6.12.92, 6.18.25, 7.0.2, 7.1
- linux Debian 13 6.12.94-1
- linux Debian 14 7.0.3-1
debian advisories DEBIAN-CVE-2026-31717
- 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-31717
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-source openSUSE Tumbleweed 7.0.7-1.1
opensuse advisories openSUSE-SU-2026:10793-1
- git.kernel.org/stable/c/712cdf917e77a6444ce3836874829d770db20ee6 commit
- git.kernel.org/stable/c/c7f0f0d01c88bdcb8b1694d7d321670013f7ed7d commit
- git.kernel.org/stable/c/00ce8d6789dae72d042a4522264964c72891ca37 commit
- git.kernel.org/stable/c/c908c853f304a4969b5aa10eba0b50350cc65b80 commit
- git.kernel.org/stable/c/49110a8ce654bbe56bef7c5e44cce31f4b102b8a 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-31717 updated
kernel: ksmbd: validate owner of durable handle on reconnect
-
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.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/712cdf917e77a6444ce3836874829d770db20ee6
- git.kernel.org /stable/c/c7f0f0d01c88bdcb8b1694d7d321670013f7ed7d
-
git.kernel.org
/stable/c/00ce8d6789dae72d042a4522264964c72891ca37
patch
-
git.kernel.org
/stable/c/c908c853f304a4969b5aa10eba0b50350cc65b80
patch
-
git.kernel.org
/stable/c/49110a8ce654bbe56bef7c5e44cce31f4b102b8a
patch
Sources
- CVE List CVE-2026-31717
- NVD CVE-2026-31717
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.