Skip to main content
VulnerabilityPublished Updated

CVE-2026-68083: Linux kernel · ksmbd: fix path resolution in ksmbd_vfs_kern_path_create

Affects Linux kernelSource CVE Database V5

0

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

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 265fd1991c1db85fbabaad4946ca0e63e2ae688d, < c7c884a1305aa4540eb7942a50bd356b34120e1f
Fixed in
  • c7c884a1305aa4540eb7942a50bd356b34120e1f
LinuxLinuxAffected
  • ≥ 265fd1991c1db85fbabaad4946ca0e63e2ae688d, < a2516be69048856e2a49a51e00975dc59431f95c
Fixed in
  • a2516be69048856e2a49a51e00975dc59431f95c
LinuxLinuxAffected
  • ≥ 265fd1991c1db85fbabaad4946ca0e63e2ae688d, < 98185b3025beeae92d1fe700d5db26b9ac4bf025
Fixed in
  • 98185b3025beeae92d1fe700d5db26b9ac4bf025
LinuxLinuxAffected
  • ≥ 265fd1991c1db85fbabaad4946ca0e63e2ae688d, < 489d1ded01425c0fb33418172c0e4e588467526b
Fixed in
  • 489d1ded01425c0fb33418172c0e4e588467526b
LinuxLinuxAffected
  • ≥ 265fd1991c1db85fbabaad4946ca0e63e2ae688d, < 1c8951963d8ed357f70f59e0ad4ddce2199d2016
Fixed in
  • 1c8951963d8ed357f70f59e0ad4ddce2199d2016
LinuxLinuxAffected
  • =5.15
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

Community reviews

Loading reviews…