Skip to main content
Vulnerability Database/CVE-2026-93786

CVE-2026-93786: Linux Kernel POSIX ACL Privilege Escalation

CVE-2026-93786 is a privilege escalation flaw in Linux kernel ksmbd affecting POSIX ACL handling. The vulnerability allows SMB object creation to widen effective permissions. This article covers technical details, impact, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-93786 Overview

CVE-2026-93786 is a Linux kernel vulnerability in the ksmbd SMB server. The flaw causes ksmbd to overwrite the VFS-computed POSIX Access Control List (ACL) when SMB clients create objects on a share. By mutating the parent ACL and discarding the child's inherited access and default ACLs, the server widens effective permissions beyond what the restrictive ACL_MASK entry allows. An authenticated SMB user can create files or directories with permissions broader than the parent directory's inheritance rules intend. The result is unintended read and write access to inherited paths.

Critical Impact

Authenticated remote SMB users can create objects whose effective permissions bypass restrictive POSIX ACL mask entries, exposing confidential files and allowing unauthorized modification.

Affected Products

  • Linux kernel versions containing the ksmbd in-kernel SMB server with the defective ACL inheritance logic
  • Linux distributions that ship and enable ksmbd for SMB file sharing
  • Any Linux host exporting shares via ksmbd to networked SMB clients

Discovery Timeline

  • 2026-09-24 - CVE-2026-93786 published to the National Vulnerability Database
  • 2026-09-25 - Last updated in NVD database

Technical Details for CVE-2026-93786

Vulnerability Analysis

The Linux Virtual File System (VFS) layer computes a child object's POSIX ACL from the parent directory's default ACL combined with the requested creation mode. This process honors the ACL_MASK entry, which caps the maximum effective permissions granted to named users, named groups, and the owning group.

In the vulnerable ksmbd code path, the server mutates the parent's default ACL during inheritance and then overwrites the VFS-computed access and default ACLs on the newly created child. The restrictive mask entry is lost, so permissions on SMB-created files and directories expand beyond the intended ceiling.

An attacker with authenticated SMB access can exploit this by issuing standard SMB CREATE requests against directories that rely on POSIX ACL masks for confidentiality or integrity. The resulting objects grant group members or named ACL entries higher effective permissions than the share administrator configured.

Root Cause

The root cause is improper handling of inherited POSIX ACLs inside ksmbd during object creation. The code modifies the parent ACL in place and replaces the child's VFS-derived access and default ACLs instead of preserving them. This design discards the ACL_MASK constraint that limits effective permissions, producing a broken access control condition.

Attack Vector

Exploitation requires network reachability to the ksmbd service and valid SMB credentials. The attacker performs normal SMB file or directory creation operations within shares whose parent directories carry restrictive default ACLs. No special protocol extensions or malformed packets are required. The server itself widens the permissions during creation, so the attacker interacts only with the standard SMB2 CREATE flow. The vulnerability affects confidentiality and integrity but does not impact availability.

No verified proof-of-concept code is published. Technical details are available in the upstream kernel commits referenced in the Kernel Git Commit Fix and the Kernel Git Commit Patch.

Detection Methods for CVE-2026-93786

Indicators of Compromise

  • Files or directories inside ksmbd shares whose POSIX ACLs show effective permissions exceeding the parent directory's mask:: entry
  • Objects created over SMB where getfacl output lacks the expected restrictive mask entry inherited from the parent default ACL
  • Unexpected read or write success by SMB users against inherited paths that should be constrained by named-user or named-group ACL entries

Detection Strategies

  • Audit POSIX ACLs on ksmbd-exported directories with getfacl -R and compare named-entry effective permissions against the parent default ACL mask
  • Enable kernel audit rules on ksmbd share paths to log file and directory creation events, then correlate with SMB session identities
  • Review SMB server logs for authenticated sessions that create objects in directories using default ACL inheritance

Monitoring Recommendations

  • Collect filesystem and SMB authentication telemetry centrally and alert when newly created objects deviate from baseline ACL templates
  • Track installed kernel versions across the Linux fleet and flag hosts running ksmbd on unpatched builds
  • Monitor ksmbd.mountd and kernel logs for configuration reloads and share mounts that could re-expose vulnerable code paths

How to Mitigate CVE-2026-93786

Immediate Actions Required

  • Apply the upstream kernel update that restores VFS-inherited POSIX ACL mask handling in ksmbd
  • Inventory all Linux hosts running ksmbd and prioritize patching for systems exposing shares to untrusted networks or multi-tenant users
  • Re-audit POSIX ACLs on shares after patching and reset any objects whose permissions were widened before remediation

Patch Information

The fix is committed upstream in the Linux kernel stable tree. Reference the Kernel Git Commit Update, the Kernel Git Commit Fix, and the Kernel Git Commit Patch. Distribution vendors backport these commits into supported stable kernels. Install the vendor-supplied kernel package and reboot to activate the corrected ksmbd code.

Workarounds

  • Disable the ksmbd kernel module on hosts that do not require in-kernel SMB serving and migrate to a user-space SMB server if feasible
  • Restrict network access to TCP port 445 on ksmbd hosts using host-based firewalls so only trusted clients can reach the service
  • Remove reliance on POSIX ACL mask entries for enforcement on ksmbd shares until patched, substituting coarser mode bits or share-level access rules
bash
# Temporarily unload the ksmbd module and block SMB access
sudo systemctl stop ksmbd.service
sudo modprobe -r ksmbd
sudo iptables -A INPUT -p tcp --dport 445 -j DROP

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.