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.
Published: 2026-08-10
Score: 9.1 Critical
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The kernel’s ksmbd service performs path resolution for create, mkdir, and hardlink operations without the LOOKUP_BENEATH restriction that protects read lookups. The function ksmbd_vfs_kern_path_create builds an absolute path with convert_to_unix_name() and walks it from AT_FDCWD, which lets an authenticated SMB client include a '..' component that is resolved relative to the real filesystem root. When a race occurs while a missing component causes the lookup to fail, the subsequent create walk can escape the share and access any file on the host. This flaw is a classic directory traversal (CWE‑22) that permits reading or modifying files outside the intended share, provided the attacker has valid SMB credentials and can reach the SMB service.

Affected Systems

Linux kernels that lack the patch identified by commit 1c8951963d8ed357f70f59e0ad4ddce2199d2016. The affected product is the Linux kernel shipped by Linux:Linux, with no specific version range supplied; any kernel built before this commit is vulnerable.

Risk and Exploitability

The CVSS score of 9.1 reflects a high severity impact, while the EPSS score of < 1% indicates that the likelihood of exploitation is currently low. The vulnerability is not listed in the CISA KEV catalog. Exploitation requires network connectivity to the SMB port (typically TCP 445), valid SMB credentials, and a race condition where the create path resolves a '..' component after the lookup has failed. Once achieved, the attacker gains unauthorized access to arbitrary files on the host, which could lead to privilege escalation or data theft.

Generated by OpenCVE AI on August 14, 2026 at 03:02 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply a kernel update that includes the ksmbd path‑resolution fix (commit 1c8951963d8ed357f70f59e0ad4ddce2199d2016).
  • If an immediate kernel upgrade is not possible, restrict SMB share permissions to prevent directory creation that could contain '..' components, for example by setting the share to read‑only or applying strict path validation at the ACL level.
  • Rebuild the kernel with the patch applied if you must patch manually, then reboot to load the updated module.

Generated by OpenCVE AI on August 14, 2026 at 03:02 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 13 Aug 2026 22:45:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 9.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H'}


Tue, 11 Aug 2026 00:15:00 +0000


Mon, 10 Aug 2026 20:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-22

Mon, 10 Aug 2026 12:00:00 +0000

Type Values Removed Values Added
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.
Title ksmbd: fix path resolution in ksmbd_vfs_kern_path_create
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-17T04:58:30.819Z

Reserved: 2026-07-30T09:28:09.367Z

Link: CVE-2026-68083

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-10T12:17:20.807

Modified: 2026-08-17T05:18:07.487

Link: CVE-2026-68083

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-08-10T00:00:00Z

Links: CVE-2026-68083 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-14T03:15:12Z

Weaknesses
  • CWE-22

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')