Skip to content
Threat Brief

← All advisories

CVE-2026-97555

High 8.8No known exploitationFix available

smb: client: fix heap overflow in DACL owner/group rewrite

Record last updated

CVSS score

8.8

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.7%

Higher than 53% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

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)

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
msrc.microsoft.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom bc3e9dd9d104ca1b75644eab87b38ce8a924aef4 before 2a9aee9ef5622d58d8aafaa3263b3ffe70e2d9dd2a9aee9ef5622d58d8aafaa3263b3ffe70e2d9ddCVE Program
LinuxLinuxfrom bc3e9dd9d104ca1b75644eab87b38ce8a924aef4 before 0ee150794c75bcd0be0e24ff3394f433cbae18cc0ee150794c75bcd0be0e24ff3394f433cbae18ccCVE Program
LinuxLinuxfrom bc3e9dd9d104ca1b75644eab87b38ce8a924aef4 before 4e78b5ff13214353750b87283ff79f62510f58444e78b5ff13214353750b87283ff79f62510f5844CVE Program
LinuxLinuxfrom bc3e9dd9d104ca1b75644eab87b38ce8a924aef4 before 63c2fbde15ffc9a0c21adf670c38d028e20fa65c63c2fbde15ffc9a0c21adf670c38d028e20fa65cCVE Program
LinuxLinuxfrom bc3e9dd9d104ca1b75644eab87b38ce8a924aef4 before d5cea6766ae1868a51c7d17d77d065b4f55c587fd5cea6766ae1868a51c7d17d77d065b4f55c587fCVE Program
LinuxLinuxfrom bc3e9dd9d104ca1b75644eab87b38ce8a924aef4 before fb736ab4fb8c4fdb8b2f9ccd3a62e03d11549ca1fb736ab4fb8c4fdb8b2f9ccd3a62e03d11549ca1CVE Program
LinuxLinuxfrom bc3e9dd9d104ca1b75644eab87b38ce8a924aef4 before 7fa84c9ca690643f429ae2709584a47e74b572c97fa84c9ca690643f429ae2709584a47e74b572c9CVE Program
LinuxLinux5.12Not documentedCVE Program
Microsoftazl3 kernel 6.6.157.1-1 on Azure Linux 3.0Not documented6.6.158.1-1Microsoft MSRC
Microsoftazl4 kernel 6.18.50-1.5.azl4 on Azure Linux 4.0Not documented0:6.18.57-1.1.azl4Microsoft MSRC
LinuxLinux (unaffected)from 5.15.224 up to and including 5.15.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.1.191 up to and including 6.1.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.111 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.53 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.6.158 up to and including 6.6.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.2.7 up to and including 7.2.*Not documentedCVE Program
LinuxLinux (unaffected)7.3Not documentedCVE Program
LinuxLinux (unaffected)all versions before 5.12Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  3. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  4. Advisory change

    Microsoft advisory revised (3.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  5. Advisory change

    Microsoft advisory revised (4.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  6. Advisory change

    Microsoft advisory revised (5.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  7. Advisory change

    Microsoft advisory revised (6.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  8. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references