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

ksmbd: fix maximum allowed access checks

The DACL permission check looks for an ACE matching the current user and
falls back to the Everyone ACE. It does not consider an Authenticated
Users ACE, even though an authenticated session is a member of that
well-known group.

As a result, opening a file whose access is granted through S-1-5-11 can
incorrectly fail with STATUS_ACCESS_DENIED. Treat an Authenticated Users
ACE as a fallback entry alongside Everyone.

The maximal access calculation also combines access masks from every ACE,
regardless of whether its SID applies to the current user. This can grant
rights belonging to an unrelated principal. Process only ACEs applying to
the user, Everyone, or Authenticated Users, and accumulate allowed and
denied masks in ACL order. Preserve explicitly requested access bits so
they are validated against the resulting maximal mask.

When ACCESS_SYSTEM_SECURITY is denied, report STATUS_PRIVILEGE_NOT_HELD
instead of the generic STATUS_ACCESS_DENIED. Access to the system ACL
requires a security privilege that ksmbd does not grant.

For regular files, include FILE_EXECUTE in maximal access when the client
requested GENERIC_EXECUTE and the DACL grants the complete file-read set.
Keep a direct FILE_EXECUTE request subject to the explicit DACL bit. This
matches the POSIX file ACL mapping without broadening specific execute
requests.

Do not replace rights from an applicable NT ACE with a POSIX ACL entry.
The POSIX ACL is only a fallback when no user, Everyone, or Authenticated
Users ACE applies; otherwise it can incorrectly broaden the stored DACL.

This fixes smb2.maximum_allowed.maximum_allowed.
Published: 2026-09-24
Score: 8.1 High
EPSS: < 1% Very Low
KEV: No
Impact: Access Control Failure
Action: Immediate Patch
AI Analysis

Impact

The vulnerability in the Linux kernel’s ksmbd component causes the DACL permission checks to ignore Authenticated Users ACE entries and to aggregate all ACE access masks without filtering for the correct subject. As a result, a file that should be accessible to an authenticated user may be denied, and conversely, permissions belonging to an unrelated principal can be incorrectly granted. This mis‑authorization can lead to either denial of legitimate access or unauthorized escalation of file privileges. The flaw manifests as status codes such as STATUS_ACCESS_DENIED or STATUS_PRIVILEGE_NOT_HELD, undermining the expected security boundaries enforced by SMB clients. The weakness pertains to improper authorization logic, directly impacting confidentiality, integrity, and availability of protected files.

Affected Systems

All Linux kernel installations that provide the ksmbd SMB server component are affected. The advisory does not specify particular kernel releases, which suggests that any version containing the unpatched ksmbd access‑check logic could be vulnerable. Administrators should determine whether their current kernel includes the ksmbd components described and plan for an update if the kernel is older or otherwise unpatched.

Risk and Exploitability

With a CVSS score of 8.1, the vulnerability is considered high severity. The EPSS score is < 1%, indicating a very low but non‑zero exploitation probability. The nature of the flaw—triggered via SMB file access requests on a remote host—implies that a network attacker could exploit it by authenticating to a ksmbd service and manipulating ACL entries or crafted file access requests. The vulnerability is not listed in the CISA KEV catalog, indicating that no publicly known exploits have been confirmed at this time. However, the remote exploitation potential and the high CVSS score warrant preemptive remediation.

Generated by OpenCVE AI on October 1, 2026 at 18:46 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest kernel update that includes the ksmbd permission‑check fix.
  • If installing the update is not immediately feasible, disable or restrict ksmbd services using systemd or network firewall rules to eliminate exposure.
  • Continuously monitor SMB logs for unauthorized access attempts and enforce stricter ACL management policies to prevent accidental mis‑configuration.

Generated by OpenCVE AI on October 1, 2026 at 18:46 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 15 Oct 2026 13:30:00 +0000


Tue, 29 Sep 2026 13:15:00 +0000


Fri, 25 Sep 2026 05:15:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

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


Thu, 24 Sep 2026 16:00:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix maximum allowed access checks The DACL permission check looks for an ACE matching the current user and falls back to the Everyone ACE. It does not consider an Authenticated Users ACE, even though an authenticated session is a member of that well-known group. As a result, opening a file whose access is granted through S-1-5-11 can incorrectly fail with STATUS_ACCESS_DENIED. Treat an Authenticated Users ACE as a fallback entry alongside Everyone. The maximal access calculation also combines access masks from every ACE, regardless of whether its SID applies to the current user. This can grant rights belonging to an unrelated principal. Process only ACEs applying to the user, Everyone, or Authenticated Users, and accumulate allowed and denied masks in ACL order. Preserve explicitly requested access bits so they are validated against the resulting maximal mask. When ACCESS_SYSTEM_SECURITY is denied, report STATUS_PRIVILEGE_NOT_HELD instead of the generic STATUS_ACCESS_DENIED. Access to the system ACL requires a security privilege that ksmbd does not grant. For regular files, include FILE_EXECUTE in maximal access when the client requested GENERIC_EXECUTE and the DACL grants the complete file-read set. Keep a direct FILE_EXECUTE request subject to the explicit DACL bit. This matches the POSIX file ACL mapping without broadening specific execute requests. Do not replace rights from an applicable NT ACE with a POSIX ACL entry. The POSIX ACL is only a fallback when no user, Everyone, or Authenticated Users ACE applies; otherwise it can incorrectly broaden the stored DACL. This fixes smb2.maximum_allowed.maximum_allowed.
Title ksmbd: fix maximum allowed access checks
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-10-15T10:11:49.159Z

Reserved: 2026-09-17T16:02:15.098Z

Link: CVE-2026-93282

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-24T16:17:25.570

Modified: 2026-10-15T11:18:07.960

Link: CVE-2026-93282

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-09-24T00:00:00Z

Links: CVE-2026-93282 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-01T19:00:16Z

Weaknesses
  • CWE-266

    Incorrect Privilege Assignment