Linux vulnerability

In the Linux kernel, the following vulnerability has been resolved: ksmbd: validate ACE size against SID sub-authorities set_ntacl_dacl() validates sid.num_subauth before copying an ACE, but does not verify that the declared ACE size contains all sub-authorities described by that field. An undersized ACE can therefore be copied and later make the POSIX ACL deduplication walk inspect data beyond the copied ACE boundary. The existing initial bound check is also too small. It only ensures that the ACE size field is accessible before set_ntacl_dacl() reads sid.num_subauth farther into the input buffer. Require enough input for the fixed SID header before accessing num_subauth, reject ACEs smaller than that header, and skip ACEs whose declared size cannot contain the complete SID. This makes the validation consistent with the other ACE walk paths.

Published 10 Aug 2026Updated 3 Oct 20266 sources
CVSS 8.8

What happened

In the Linux kernel, the following vulnerability has been resolved: ksmbd: validate ACE size against SID sub-authorities set_ntacl_dacl() validates sid.num_subauth before copying an ACE, but does not verify that the declared ACE size contains all sub-authorities described by that field. An undersized ACE can therefore be copied and later make the POSIX ACL deduplication walk inspect data beyond the copied ACE boundary. The existing initial bound check is also too small. It only ensures that the ACE size field is accessible before set_ntacl_dacl() reads sid.num_subauth farther into the input buffer. Require enough input for the fixed SID header before accessing num_subauth, reject ACEs smaller than that header, and skip ACEs whose declared size cannot contain the complete SID. This makes the validation consistent with the other ACE walk paths.

Affected versions

Linux: e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 through before 5a2d9fe0e87c71baa0aaa1cfc1361892fcd1ece0 (git); e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 through before b7cb5bf0855470799f12da825de91e48951b3876 (git); e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 through before 62d80d7c2d9428085e7458ad4c06ca8c0984039b (git); e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 through before 337022d9dfac441c3b35e4455a51aa981996e02e (git); e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 through before 61fd3559199f7fa693dcbff35e59477e24af041a (git); e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 through before 5152c6d49e3fd4e9f2e857c57527aead752f1f87 (git); 5.15 Fixed: See vendor advisory.

Why it matters

Review the vendor advisory and exposure of the affected product to determine operational impact.

Detection & mitigation

  • Apply vendor-provided updates or mitigations.
  • Review affected product exposure and access logs.

Public PoC references

No public PoC reference has passed the current publication threshold.