CVE-2026-68083: Linux kernel · ksmbd: fix path resolution in ksmbd_vfs_kern_path_create
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical · fixed in c7c884a1305aa4540eb7942a50bd356b34120e1f : patch Linux kernel as a priority.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in c7c884a1305aa4540eb7942a50bd356b34120e1f, a2516be69048856e2a49a51e00975dc59431f95c, 98185b3025beeae92d1fe700d5db26b9ac4bf025 +2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix path resolution in ksmbd_vfs_kern_path_create The SMB2 open lookup is rooted at the share with LOOKUP_BENEATH, but the create/mkdir/hardlink sink is not: ksmbd_vfs_kern_path_create() builds an absolute path with convert_to_unix_name() and resolves it from AT_FDCWD via start_creating_path(), so a ".." component is walked from the real filesystem root and escapes the export. An authenticated client races a missing path component so the rooted open lookup returns -ENOENT (taking the create branch) while the same component is present (a directory) when the create walk runs; the create then resolves ".." out of the share. Root the create walk at the share like the lookup and rename paths already are: resolve the parent with vfs_path_parent_lookup(..., LOOKUP_BENEATH, &share_conf->vfs_path) and create the final component with start_creating_noperm(). convert_to_unix_name() then has no callers and is removed.
References
- git.kernel.org/stable/c/a2516be69048856e2a49a51e00975dc59431f95c (opens in a new tab)
- git.kernel.org/stable/c/489d1ded01425c0fb33418172c0e4e588467526b (opens in a new tab)
- git.kernel.org/stable/c/c7c884a1305aa4540eb7942a50bd356b34120e1f (opens in a new tab)
- git.kernel.org/stable/c/98185b3025beeae92d1fe700d5db26b9ac4bf025 (opens in a new tab)
- git.kernel.org/stable/c/1c8951963d8ed357f70f59e0ad4ddce2199d2016 (opens in a new tab)