CVE-2026-97559

published 25 Sep 2026 · updated 19 Nov 2026

smb: client: fail DACL rewrite when the new DACL exceeds 64K

4.3MediumCVSS 4.3EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f033d6e5aadf3e8c6a12873110557ed40cd71388, Kernel 284877c6189fda1ac3d81771dd8482660a0c7dc1, Kernel 2ef532a01f44687f5b95001e88247cf05bff9892 and 8 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=f5065508897a922327f32223082325d10b069ebc <f033d6e5aadf3e8c6a12873110557ed40cd71388, >=f5065508897a922327f32223082325d10b069ebc <284877c6189fda1ac3d81771dd8482660a0c7dc1, >=f5065508897a922327f32223082325d10b069ebc <2ef532a01f44687f5b95001e88247cf05bff9892, >=f5065508897a922327f32223082325d10b069ebc <d05045177a855386bca5e1909e08d06290e6e3b3, >=f5065508897a922327f32223082325d10b069ebc <d433376abc47e10870ae732f89c7c1a60b199a0c, >=f5065508897a922327f32223082325d10b069ebc <ee13d687d06a6fbb2008625dd560c654231b28e0, =5.12f033d6e5aadf3e8c6a12873110557ed40cd71388, 284877c6189fda1ac3d81771dd8482660a0c7dc1, 2ef532a01f44687f5b95001e88247cf05bff9892, d05045177a855386bca5e1909e08d06290e6e3b3, d433376abc47e10870ae732f89c7c1a60b199a0c, ee13d687d06a6fbb2008625dd560c654231b28e0
linux-kernel: Kernel>=6.13.0 <6.18.53, >=6.19.0 <7.2.7, >=6.2.0 <6.6.160, >=6.7.0 <6.12.112, >=5.12.0 <6.1.1916.18.53, 7.2.7, 6.6.160, 6.12.112, 6.1.191

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-97559 severity on Zeptric[![CVE-2026-97559](https://zeptric.io/badge/cve/CVE-2026-97559.svg)](https://zeptric.io/cve/CVE-2026-97559)