VulnerabilityPublished 24 Sep 2026Updated 30 Oct 2026

CVE-2026-93282: Linux kernel · ksmbd: fix maximum allowed access checks

Source GCVE Database

Authoritative record:CVE-2026-93282· High 8.1

Not known to be exploited · CVSS 8.1 High · fixed in faf0b894eedc7b2ebb36c48d04d412240dd0ea71 : patch Linux kernel soon.

Data as of 30 Oct 2026, 16:33 UTC

CVSS 3.1 base score

8.1High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (Linux)	CVSS 3.1	8.1

Patch: Available – fixed in faf0b894eedc7b2ebb36c48d04d412240dd0ea71, cc2f133e80eb2c4a04bfa77a2f207749fe2f516a, 37459edb69c094553026ee48c2cc2acc657f9f43 +3

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

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

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-7xq8-4f3j-v3g7

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, < faf0b894eedc7b2ebb36c48d04d412240dd0ea71	Fixed in faf0b894eedc7b2ebb36c48d04d412240dd0ea71
LinuxLinux	Affected ≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, < cc2f133e80eb2c4a04bfa77a2f207749fe2f516a	Fixed in cc2f133e80eb2c4a04bfa77a2f207749fe2f516a
LinuxLinux	Affected ≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, < 37459edb69c094553026ee48c2cc2acc657f9f43	Fixed in 37459edb69c094553026ee48c2cc2acc657f9f43
LinuxLinux	Affected ≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, < 28289d880e6d11ae7ac77b81af3312453febf939	Fixed in 28289d880e6d11ae7ac77b81af3312453febf939
LinuxLinux	Affected ≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, < 35d5c59fe6b1d9fe43fb14eb384f69ee1a120f9c	Fixed in 35d5c59fe6b1d9fe43fb14eb384f69ee1a120f9c
LinuxLinux	Affected ≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, < 7c293e83d86cfd38124f51b27882ad631818bf48	Fixed in 7c293e83d86cfd38124f51b27882ad631818bf48

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.

References

Community reviews

Loading reviews…