Skip to main content
VulnerabilityPublished Updated

CVE-2026-97559: Linux kernel · smb: client: fail DACL rewrite when the new DACL exceeds 64K

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in ee13d687d06a6fbb2008625dd560c654231b28e0 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:18 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in ee13d687d06a6fbb2008625dd560c654231b28e0, d05045177a855386bca5e1909e08d06290e6e3b3, d433376abc47e10870ae732f89c7c1a60b199a0c +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ f5065508897a922327f32223082325d10b069ebc, < ee13d687d06a6fbb2008625dd560c654231b28e0
Fixed in
  • ee13d687d06a6fbb2008625dd560c654231b28e0
LinuxLinuxAffected
  • ≥ f5065508897a922327f32223082325d10b069ebc, < d05045177a855386bca5e1909e08d06290e6e3b3
Fixed in
  • d05045177a855386bca5e1909e08d06290e6e3b3
LinuxLinuxAffected
  • ≥ f5065508897a922327f32223082325d10b069ebc, < d433376abc47e10870ae732f89c7c1a60b199a0c
Fixed in
  • d433376abc47e10870ae732f89c7c1a60b199a0c
LinuxLinuxAffected
  • ≥ f5065508897a922327f32223082325d10b069ebc, < 284877c6189fda1ac3d81771dd8482660a0c7dc1
Fixed in
  • 284877c6189fda1ac3d81771dd8482660a0c7dc1
LinuxLinuxAffected
  • ≥ f5065508897a922327f32223082325d10b069ebc, < 2ef532a01f44687f5b95001e88247cf05bff9892
Fixed in
  • 2ef532a01f44687f5b95001e88247cf05bff9892
LinuxLinuxAffected
  • =5.12
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: smb: client: fail DACL rewrite when the new DACL exceeds 64K replace_sids_and_copy_aces() and set_chmod_dacl() accumulate the size of the DACL they build in a u16. That accumulator can wrap. validate_dacl() caps num_aces at (dacl_size - sizeof(struct smb_acl)) / 20, i.e. 3276 for a maximally sized DACL, while each rewritten ACE can grow to sizeof(struct smb_ace) (76 bytes) once its SID is replaced with one carrying SID_MAX_SUB_AUTHORITIES sub-authorities. The worst case is therefore sizeof(struct smb_acl) + 3276 * 76 = 248984 bytes, far beyond what a u16 can hold. A wraparound is reached with 863 ACEs. After the wraparound, ndacl_ptr->size becomes meaningless and the offset will point anywhere in the ACE array. As a result, we will see corruption of the DACL, which then gets sent to the server. This is not an out-of-bounds write as the allocation now covers the worst-case expansion, so writes will always go into the buffer. Adjust the code to use a u32 internally and return -EOVERFLOW in the overflow case. The operation must be refused, because a DACL can only hold 2^16-1 bytes on the wire and larger DACLs cannot be represented. set_chmod_dacl() carries the same pattern and is fixed the same way. It only wraps once the source DACL comes within roughly 380 bytes of the 64K ceiling, but the failure mode is identical.

References

Community reviews

Loading reviews…