CVE-2026-31611

ksmbd: require 3 sub-authorities before reading sub_auth[2]

Published Apr 24, 2026 CVSS 3.1 · 8.6 High EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

ksmbd: require 3 sub-authorities before reading sub_auth[2]

parse_dacl() compares each ACE SID against sid_unix_NFS_mode and on
match reads sid.sub_auth[2] as the file mode. If sid_unix_NFS_mode is
the prefix S-1-5-88-3 with num_subauth = 2 then compare_sids() compares
only min(num_subauth, 2) sub-authorities so a client SID with
num_subauth = 2 and sub_auth = {88, 3} will match.

If num_subauth = 2 and the ACE is placed at the very end of the security
descriptor, sub_auth[2] will be 4 bytes past end_of_acl. The
out-of-band bytes will then be masked to the low 9 bits and applied as
the file's POSIX mode, probably not something that is good to have
happen.

Fix this up by forcing the SID to actually carry a third sub-authority
before reading it at all.

Analysis

AI-generated

Technical impact

The ksmbd component of the Linux kernel incorrectly processes the sub‑authority array of a Security Identifier (SID) when parsing Access Control Lists. If a SID contains only two sub‑authorities but matches the pattern S‑1‑5‑88‑3, the kernel reads sub_auth[2] beyond the allocated array. These out‑of‑bounds bytes are masked to the low nine bits and applied as the file’s POSIX mode. In effect, a client can cause the server to set arbitrary read, write, or execute permissions on files exposed via SMB, allowing privilege manipulation on shared resources. The flaw is a classic out-of-bounds read (CWE‑1285) that could lead to unintended permission changes.

Affected Systems

Affected systems are all releases of the Linux kernel that include the ksmbd subsystem and have not yet incorporated the commit that enforces a three‑sub‑authority requirement. No specific version numbers are listed in the advisory, so the risk applies to any kernel build where the vulnerability remains unpatched. The advisory lists only the generic vendor product “Linux:Linux”, indicating the issue is kernel‑wide rather than restricted to a particular distribution.

Risk and Exploitability

The vulnerability receives a CVSS score of 8.6, indicating high potential impact, while the EPSS score of under 1 percent shows a low probability of widespread exploitation at present. The attack vector is most likely remote, originating from a malicious SMB client that crafts a specially formatted ACL entry; the exploitation requires the client to supply a SID with two sub‑authorities matching the pattern S‑1‑5‑88‑3 and to place the entry at the end of the descriptor. The issue is not currently listed in CISA’s KEV catalog, which suggests no confirmed, active exploitation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the kernel to a version that includes the ksmbd fix (commit 08f9e6d8 or later).
  • Restrict SMB access to trusted clients or apply network segmentation to limit exposure of ksmbd.
  • Audit file permission changes on files served over SMB to detect unexpected mode modifications.

Generated by OpenCVE AI on April 29, 2026 at 21:37 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4665-1 linux security update
Debian DLA Debian DLA DLA-4671-1 linux-6.1 security update
Debian DSA Debian DSA DSA-6238-1 linux security update
Ubuntu USN Ubuntu USN USN-8488-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8488-2 Linux kernel (Raspberry Pi) vulnerabilities
Ubuntu USN Ubuntu USN USN-8507-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-8567-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8569-1 Linux kernel (HWE) vulnerabilities
Ubuntu USN Ubuntu USN USN-8574-1 Linux kernel (GCP FIPS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8574-2 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8595-1 Linux kernel (Oracle) vulnerabilities
Ubuntu USN Ubuntu USN USN-8596-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-8595-2 Linux kernel (AWS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8603-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8606-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8607-1 Linux kernel (Azure CVM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8608-1 Linux kernel (Azure FIPS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8609-1 Linux kernel (Azure CVM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8574-3 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8595-3 Linux kernel (AWS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8619-1 Linux kernel (HWE) vulnerabilities
Ubuntu USN Ubuntu USN USN-8665-1 Linux kernel (Raspberry Pi) vulnerabilities
History
Type Values Removed Values Added
Weaknesses NVD-CWE-noinfo
Type Values Removed Values Added
Metrics cvssV3_1

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

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: ksmbd: require 3 sub-authorities before reading sub_auth[2] parse_dacl() compares each ACE SID against sid_unix_NFS_mode and on match reads sid.sub_auth[2] as the file mode. If sid_unix_NFS_mode is the prefix S-1-5-88-3 with num_subauth = 2 then compare_sids() compares only min(num_subauth, 2) sub-authorities so a client SID with num_subauth = 2 and sub_auth = {88, 3} will match. If num_subauth = 2 and the ACE is placed at the very end of the security descriptor, sub_auth[2] will be 4 bytes past end_of_acl. The out-of-band bytes will then be masked to the low 9 bits and applied as the file's POSIX mode, probably not something that is good to have happen. Fix this up by forcing the SID to actually carry a third sub-authority before reading it at all.
Title ksmbd: require 3 sub-authorities before reading sub_auth[2]
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 15, 2026, 1:17 AM
Reserved
Mar 9, 2026, 3:48 PM
Status
Modified
Published
Apr 24, 2026, 3:16 PM
Modified
Nov 11, 2026, 11:10 PM
Severity
Public date
Apr 24, 2026, 12:00 AM