Skip to main content

Linux ksmbd EUVDEUVD-2026-86173

| CVE-2026-93786 HIGH
2026-09-24 Linux GHSA-h69q-mp6v-qjfh
8.1
CVSS 3.1 · Vendor: Linux
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate to ksmbd SMB share
  2. Delivery
    Create file/dir under directory with restrictive default ACL
  3. Exploit
    ksmbd overwrites VFS-computed ACL and drops ACL_MASK
  4. Execution
    Object created with widened effective permissions
  5. Impact
    Access data/paths beyond intended authorization

Vulnerability Assessment

Exploitation Conditions

Requires the target host to be running the Linux kernel's ksmbd (in-kernel SMB3) server with an exported share, an attacker holding a valid authenticated SMB session (PR:L), and - critically - a parent directory configured with a restrictive default POSIX ACL / ACL_MASK whose protection ksmbd erroneously discards on child object creation. Exploitation is limited by ksmbd being a niche service (most Linux SMB deployments use userspace Samba, which is unaffected), by the requirement for authentication, and by the need for the specific ACL_MASK configuration to be present - on shares without restrictive default ACLs there is nothing to widen.

Impact

This is a real but modestly-scoped authorization flaw in the Linux kernel's ksmbd in-kernel SMB3 server. The NVD/Linux CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N = 8.1) treats it as network-reachable, low-complexity, and low-privilege with high confidentiality and integrity impact - but there is NO EPSS score, NO CISA KEV listing, and NO public POC, so all signals point to no active or imminent exploitation. The scenario is a permission-widening bug, not a memory-corruption or RCE primitive: ksmbd overwrites the VFS-computed child POSIX ACLs and mutates the parent ACL after object creation, dropping restrictive ACL_MASK entries so SMB-created objects end up with broader effective permissions than intended. Two caveats temper the raw 8.1: (1) AC:L likely understates complexity - exploitation depends on a parent directory actually carrying a restrictive default ACL / ACL_MASK, which is a specific server-side filesystem configuration, arguably AC:H; and (2) the vendor tag 'Information Disclosure' understates the issue, since the primary impact is unauthorized access/integrity via widened permissions (I:H), not passive data leakage. Overall: patch on the normal maintenance cycle, not an emergency, given the niche exposure and absence of exploitation signals.

Exploit ScenarioDerived

On a server running the kernel's ksmbd SMB3 service, an authenticated SMB user creates files or directories under a share whose parent directory has a restrictive default POSIX ACL/ACL_MASK. Because ksmbd overwrites the VFS-computed child ACLs and mutates the parent ACL, the restrictive mask is lost and the new objects gain wider effective permissions than the administrator intended, allowing access that should have been denied. No public exploit code is identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 25, 2026

Permission widening in the Linux kernel's ksmbd in-kernel SMB3 server allows an authenticated SMB session holder to create files and directories whose inherited POSIX ACLs are recomputed incorrectly, discarding restrictive ACL_MASK entries that the parent directory's default ACL was intended to enforce, so newly created objects can end up more permissive than the parent's policy allows. The bug affects the ksmbd code shipped in Linux kernels before 6.18.53 and before 6.12.111, and in practice only matters where an SMB share exports a parent directory with a restrictive default POSIX ACL; userspace Samba deployments are unaffected. Vendor-released patches exist (6.18.53, 6.12.111 and 7.2) and no public exploit code has been identified at time of analysis.

RemediationAI

Apply the vendor-released kernel patches: upgrade to Linux 6.18.53 or later on the 6.18 stable line, to 6.12.111 or later on the 6.12 stable line, or to 7.2 or later; the upstream fixes are the stable commits 591acf171644de590cda245fd8595b473a1beb70, 0093909becbda22b62b39b654dbc607faed59cd0 and e148e567a9252643baa125cb65d7ae9c2c6cf68a (see the git.kernel.org links in the references). If a kernel upgrade cannot be staged immediately, the most effective compensating control is to stop exposing the in-kernel server: unload or blacklist the ksmbd module (and stop/disable the ksmbd service) and, where SMB file sharing is still required, fall back to userspace Samba, which is unaffected by this code path; the trade-off is loss of the in-kernel server's performance characteristics and any SMB3 features that depend on ksmbd-specific behaviour, plus a migration step for existing share configuration. A narrower interim measure is to deny SMB write/create access to any exported directory whose protection relies on a default POSIX ACL with a restrictive ACL_MASK, or to pre-create the sensitive objects and lock down their ACLs explicitly instead of relying on inheritance, accepting that this reduces functionality and does not fix the underlying kernel bug. Keep ksmbd reachable only by authenticated, trusted principals (the flaw requires a valid SMB session), and monitor for anomalous object creation or permission changes inside ACL-protected shares. No public exploit code has been identified at time of analysis, so prioritise the kernel update over emergency containment.

Affected VersionsENISA

Linux 0 <6.18.53
Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0093909becbda22b62b39b654dbc607faed59cd0
Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e148e567a9252643baa125cb65d7ae9c2c6cf68a
Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <591acf171644de590cda245fd8595b473a1beb70
Linux 0 <6.12.111
Linux patch: 6.18.53
Linux patch: 6.12.111
Linux patch: 7.2

Affected Packages

euvd linux fix: 6.12.111, 6.18.53

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

ksmbd is the in-kernel SMB3 server merged into the Linux kernel (distinct from the long-standing userspace Samba daemon), and it maps SMB create operations onto normal VFS object creation. When a new file or directory is created under a directory carrying a default POSIX ACL, the VFS (via the POSIX ACL inheritance path) computes the child's access and default ACLs from the parent's default ACL combined with the creation mode requested by the caller. The defect is that ksmbd subsequently mutated the parent ACL and/or overwrote the child's VFS-computed access and default ACLs, so restrictive ACL_MASK entries inherited from the parent were not preserved and the effective permissions of the newly created SMB object could be wider than the parent's default ACL dictated. This matters for vertical as well as horizontal separation on the same host: an authenticated SMB user able to create objects in such a directory (CVSS vector PR:L, i.e. authenticated) could obtain access that the ACL configuration was supposed to deny (high confidentiality and integrity impact, no availability impact in the assessed vector). The source data assigns no CWE identifier; the root cause is best characterised as improper preservation of inherited permissions during an object-creation path rather than a memory-safety defect. Fixes are the upstream stable commits referenced from git.kernel.org (591acf171644de590cda245fd8595b473a1beb70, 0093909becbda22b62b39b654dbc607faed59cd0 and e148e567a9252643baa125cb65d7ae9c2c6cf68a), which stop ksmbd from mutating the parent ACL and from clobbering the child's VFS-computed ACLs. CPE data lists the affected package simply as linux:linux, confirming this is a kernel-level flaw rather than a flaw in a separate Samba package.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Linux) PRIMARY 8.1 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
vuln.today AI 6.8 MEDIUM

Network SMB service with authenticated user (PR:L); AC:H because exploitation depends on a parent directory carrying a restrictive default ACL/ACL_MASK; permission-widening yields C:H/I:H, no availability impact.

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
4.0 AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
SUSE 5.4 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Red Hat 5.5 MEDIUM

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Lifecycle Timeline

4
CVSS changed
Sep 25, 2026 - 05:23 NVD
8.1 (HIGH)
Patch available
Sep 24, 2026 - 17:03 EUVD
CVE Published
Sep 24, 2026 - 16:02 cve.org
UNKNOWN (no severity yet)
CVE Published
Sep 24, 2026 - 16:02 cve.org
HIGH 8.1

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

ksmbd: preserve VFS inherited POSIX ACL mask

The VFS initializes a child's POSIX ACL from the parent's default ACL and the requested creation mode. Do not mutate the parent ACL or overwrite the child's VFS-computed access and default ACLs afterwards.

This preserves restrictive ACL_MASK entries and prevents SMB object creation from widening effective permissions.

Executive ViewAI

Why It Matters

A permission-widening flaw in the Linux kernel's in-kernel ksmbd SMB3 server (CVE-2026-93786) can cause files and directories created on affected SMB shares to inherit weaker permissions than the parent directory's default POSIX ACL intended, potentially exposing sensitive content to users who should not have access. Only organizations running ksmbd on kernels earlier than 6.18.53 or 6.12.111, and only where an SMB share exports a parent directory with a restrictive default POSIX ACL, are exposed; userspace Samba deployments are unaffected. Patches are already available and no public exploit has been identified, so this is a contained configuration-and-patching issue rather than an active breach risk.

Business Impact: Medium
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 77% exploitable
Prevalence
Low
ksmbd is a niche in-kernel SMB server, rarely enabled versus userspace Samba
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
Medium

Priority Score

40
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +40
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy