ksmbd: OOB read regression in smb_check_perm_dacl() ACE-walk loops
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 151b1799861fde38087c08f613abc2843ef597b0 · < 4f7c131d2bdd7cd64b96f60d10be5ea72253f520| No fix yet |
| Linux Linux |
| No fix yet |
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: OOB read regression in smb_check_perm_dacl() ACE-walk loops
Commit d07b26f39246 ("ksmbd: require minimum ACE size in smb_check_perm_dacl()") introduced a transposed bounds check:
if (offsetof(struct smb_ace, sid) + aces_size < CIFS_SID_BASE_SIZE)
Since offsetof(..sid) is 8 and CIFS_SID_BASE_SIZE is 8, this evaluates to `aces_size < 0`. Because `aces_size` is always non-negative, this check becomes dead code and never breaks the loop.
Worse, that commit removed the old 4-byte guard, meaning the loop now reads `ace->size` (offset 2) even when `aces_size` is 0-3 bytes. This re-opens a 2-byte heap out-of-bounds (OOB) read past the pntsd allocation during subsequent SMB2_CREATE operations.
Fix this by properly transposing the comparison to require at least 16 bytes (8-byte offset + 8-byte SID base), matching the correct form used in smb_inherit_dacl().
From the CVE record · Linux
A bounds-check regression in the Linux kernel's ksmbd permission-checking code allows a two-byte heap out-of-bounds read during subsequent SMB2_CREATE operations. The input does not specify whether authentication or user interaction is required.
Engineers running Linux kernels with ksmbd should check whether their kernel includes the affected regression; affected versions are not specified.