Linux
smb: client: fix heap overflow in DACL owner/group rewrite
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix heap overflow in DACL owner/group rewrite When id_mode_to_cifs_acl rewrites an existing DACL, it allocates a buffer sized according to the on-disk DACL length reported by dacl_ptr->size. However, replace_sids_and_copy_aces may rewrite each ACE with a new owner/group SID obtained from the cifs.idmap upcall. Those SIDs can have up to SID_MAX_SUB_AUTHORITIES (15) sub-authorities, making each ACE up to 76 bytes (sizeof(struct smb_ace)). If the original DACL contains short SIDs (e.g., 1 sub-authority) while the replacement SIDs are long, the rewritten ACEs overflow the allocation. Fix this by always budgeting for worst-case SID expansion: allocate sizeof(struct smb_acl) plus num_aces * sizeof(struct smb_ace), which covers the smb_acl header and room for every ACE at maximum SID size. This replaces the previous split logic that used dacl_ptr->size for cifsacl mounts but num_aces * sizeof(struct smb_ace) for mode_from_sid mounts: both paths can trigger the same rewrite and need the same headroom. KASAN reports this as: BUG: KASAN: slab-out-of-bounds in build_sec_desc+0x1e8a/0x2680 [cifs] Write of size 4 at addr ffff8881a5e25374 by task chown/5298 ... The buggy address is located 0 bytes to the right of allocated 884-byte region [ffff8881a5e25000, ffff8881a5e25374)
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= bc3e9dd9d104ca1b75644eab87b38ce8a924aef4, < 4e78b5ff13214353750b87283ff79f62510f5844
- >= bc3e9dd9d104ca1b75644eab87b38ce8a924aef4, < 63c2fbde15ffc9a0c21adf670c38d028e20fa65c
- >= bc3e9dd9d104ca1b75644eab87b38ce8a924aef4, < d5cea6766ae1868a51c7d17d77d065b4f55c587f
- >= bc3e9dd9d104ca1b75644eab87b38ce8a924aef4, < fb736ab4fb8c4fdb8b2f9ccd3a62e03d11549ca1
- >= bc3e9dd9d104ca1b75644eab87b38ce8a924aef4, < 7fa84c9ca690643f429ae2709584a47e74b572c9
- >= bc3e9dd9d104ca1b75644eab87b38ce8a924aef4, < 2a9aee9ef5622d58d8aafaa3263b3ffe70e2d9dd
- >= bc3e9dd9d104ca1b75644eab87b38ce8a924aef4, < 0ee150794c75bcd0be0e24ff3394f433cbae18cc
Fixed in 4e78b5ff13214353750b87283ff79f62510f5844, 63c2fbde15ffc9a0c21adf670c38d028e20fa65c, d5cea6766ae1868a51c7d17d77d065b4f55c587f, fb736ab4fb8c4fdb8b2f9ccd3a62e03d11549ca1, 7fa84c9ca690643f429ae2709584a47e74b572c9, 2a9aee9ef5622d58d8aafaa3263b3ffe70e2d9dd, 0ee150794c75bcd0be0e24ff3394f433cbae18cc
- 5.12
Fixed in 0, 5.15.224, 6.1.191, 6.6.158, 6.12.111, 6.18.53, 7.2.7, 7.3
Mitigation
Upgrade Linux to 4e78b5ff13214353750b87283ff79f62510f5844 or 63c2fbde15ffc9a0c21adf670c38d028e20fa65c or d5cea6766ae1868a51c7d17d77d065b4f55c587f or fb736ab4fb8c4fdb8b2f9ccd3a62e03d11549ca1 or 7fa84c9ca690643f429ae2709584a47e74b572c9 or 2a9aee9ef5622d58d8aafaa3263b3ffe70e2d9dd or 0ee150794c75bcd0be0e24ff3394f433cbae18cc or later.
Upgrade Linux to 0 or 5.15.224 or 6.1.191 or 6.6.158 or 6.12.111 or 6.18.53 or 7.2.7 or 7.3 or later.
Timeline
Days relative to CVE publicationFirst public PoC 34 days after publication; not in CISA KEV. First PoC: woshigenm/CVE-2026-97555 (created 29 Oct 2026, found by us: 14 Nov 2026).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| woshigenm/CVE-2026-97555 | 29 Oct 2026 +34 d | 14 Nov 2026 | 4 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.