ksmbd: fix path resolution in ksmbd_vfs_kern_path_create
CVE-2026-68083 · published 10 Aug 2026
How serious is it
- Severity: critical, CVSS score 9.1 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-68083?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: 265fd1991c1db85fbabaad4946ca0e63e2ae688d to < a2516be69048856e2a49a51e00975dc59431f95c, 265fd1991c1db85fbabaad4946ca0e63e2ae688d to < 489d1ded01425c0fb33418172c0e4e588467526b, 265fd1991c1db85fbabaad4946ca0e63e2ae688d to < c7c884a1305aa4540eb7942a50bd356b34120e1f, 265fd1991c1db85fbabaad4946ca0e63e2ae688d to < 98185b3025beeae92d1fe700d5db26b9ac4bf025
- Linux Linux: 5.15
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/a2516be69048856e2a49a51e00975dc59431f95c
- git.kernel.org/stable/c/489d1ded01425c0fb33418172c0e4e588467526b
- git.kernel.org/stable/c/c7c884a1305aa4540eb7942a50bd356b34120e1f
- git.kernel.org/stable/c/98185b3025beeae92d1fe700d5db26b9ac4bf025
- git.kernel.org/stable/c/1c8951963d8ed357f70f59e0ad4ddce2199d2016
Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON