CVE-2026-64393 in the critical feed json
ksmbd: run set info with opener credentials
published 2026-07-25 3 mo ago modified 2026-09-04 2 mo ago also EUVD-2026-48937
- cvss
- 9.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 41%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: run set info with opener credentials
SMB2 SET_INFO handlers call path-based VFS helpers after checking the access mask granted to the SMB handle. Those helpers perform their owner, inode permission and LSM checks using the current ksmbd worker credentials.
Run the complete SET_INFO dispatch with the credentials captured when the handle was opened. This also removes the separate security information credential setup and keeps all SET_INFO classes under one credential scope.
Direct override_creds() is used because it can nest with the request credential overrides already used by rename and link helpers.
Patch / fix
- Linux Linux 6.1.178, 6.6.145, 6.12.96, 6.18.39, 7.1.4, 7.2
- linux Debian 12 6.1.180-1
- linux Debian 13 6.12.96-1
- linux Debian 14 7.1.4-1
- linux-6.12 Debian 12 6.12.100-1~deb12u1
debian advisories DEBIAN-CVE-2026-64393
- linux Ubuntu 24.04 LTS 6.8.0-147.147
- linux Ubuntu 26.04 LTS 7.0.0-31.31
- linux-aws Ubuntu 24.04 LTS 6.8.0-1067.70
- linux-aws Ubuntu 26.04 LTS 7.0.0-1012.12
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1071.79
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1011.11
- linux-gke Ubuntu 24.04 LTS 6.8.0-1066.74
- linux-gke Ubuntu 26.04 LTS 7.0.0-1006.7
ubuntu advisories UBUNTU-CVE-2026-64393
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.1.7-1.1
opensuse advisories openSUSE-SU-2026:11476-1
- git.kernel.org/stable/c/5cbabf3a71575cd31bc7785d92d4ab42338a654b commit
- git.kernel.org/stable/c/b35afd5cf8fab236ef21117e42ee45691d4ffa7b commit
- git.kernel.org/stable/c/0ce682867fd506f61f40c76bde7e4205bde34e87 commit
- git.kernel.org/stable/c/20ee516a62989a8d505ee432f9e59525ea23984e commit
- git.kernel.org/stable/c/8cc9ec711f5255167247a9ab6a7179b787426ed7 commit
- git.kernel.org/stable/c/b383bcad3d2fe634b26efbce53e22bbb5753a520 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-64393 updated
kernel: ksmbd: run set info with opener credentials
-
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.48% chance of exploitation in the next 30 days, higher than 41% 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:N/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/5cbabf3a71575cd31bc7785d92d4ab42338a654b
patch
-
git.kernel.org
/stable/c/b35afd5cf8fab236ef21117e42ee45691d4ffa7b
patch
-
git.kernel.org
/stable/c/0ce682867fd506f61f40c76bde7e4205bde34e87
patch
-
git.kernel.org
/stable/c/20ee516a62989a8d505ee432f9e59525ea23984e
patch
-
git.kernel.org
/stable/c/8cc9ec711f5255167247a9ab6a7179b787426ed7
patch
-
git.kernel.org
/stable/c/b383bcad3d2fe634b26efbce53e22bbb5753a520
patch
Sources
- CVE List CVE-2026-64393
- NVD CVE-2026-64393
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.