CVE-2026-99309
ksmbd: fix overflow in dacloffset bounds check in build_sec_desc()
What happened?
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix overflow in dacloffset bounds check in build_sec_desc()
When the large dacl_offset is provided, dacl_offset + sizeof(struct smb_acl) overflows on 32-bit builds and the check is passed, Which makes le16_to_cpu(ppdacl_ptr->size) read out-of-bounds. This only happens for dacl_offset in range [0xFFFFFFF8, 0xFFFFFFFF]. So the oob read is max 8 bytes preceding the allocated ppntsd.
unsigned int dacl_offset = le32_to_cpu(ppntsd->dacloffset); int ppdacl_size, ntacl_size = ppntsd_size - dacl_offset;
if (!dacl_offset || (dacl_offset + sizeof(struct smb_acl) > ppntsd_size)) goto out;
Commit beff0bc9d69b ("ksmbd: fix overflow in dacloffset bounds check") fixes similar checks in other functions. But leaves this one out, because it is only valid for 32-bit builds.
Reproduced on 32-bit ARM with KASAN, by a client sending SMB2 SET_INFO(SEC) with dacloffset=0xfffffff8, then QUERY_INFO(SEC) on the same file:
BUG: KASAN: slab-out-of-bounds in build_sec_desc (fs/smb/server/smbacl.c:1105) Read of size 2 at addr c2a273fa by task kworker/1:1/35 CPU: 1 UID: 0 PID: 35 Comm: kworker/1:1 Not tainted 7.3.0-rc2+ #5 Workqueue: ksmbd-io handle_ksmbd_work Call trace: kasan_check_range from build_sec_desc (fs/smb/server/smbacl.c:1105) build_sec_desc from smb2_query_info (fs/smb/server/smb2pdu.c:7676) smb2_query_info from handle_ksmbd_work (fs/smb/server/server.c:160) handle_ksmbd_work from process_one_work (kernel/workqueue.c:3401) process_one_work from worker_thread (kernel/workqueue.c:3473) worker_thread from kthread (kernel/kthread.c:436)
Add overflow check.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: 8f0541186e9ad1b62accc9519cc2b7a7240272a7 to < bd92e03122f33c159b552867a4abc098d405dfed; affected: 8f0541186e9ad1b62accc9519cc2b7a7240272a7 to < 4f238380ea3803afdc815c615521c6f6b13989a3; affected: 8f0541186e9ad1b62accc9519cc2b7a7240272a7 to < d1e92aa651caa352261fb3b78460b7722357835c; affected: 8f0541186e9ad1b62accc9519cc2b7a7240272a7 to < eb96e2a0e817807c48dc8387ca6a5249fdeae3a0; affected: cb69d4d6f709f87c94afa28ae64c501576692171; affected: 6e8f4abf584253cbaa596ea4ad13110cf61cd4c9; affected: 8e33102309bd6839b2e2e158f93a7b378cb4655d; affected: 5.15.62 to < 5.16; affected: 5.18.18 to < 5.19; affected: 5.19.2 to < 5.20 | See vendor advisory |
| LinuxLinux | affected: 6.0; unaffected: 0 to < 6.0; unaffected: 6.12.117 to ≤ 6.12.*; unaffected: 6.18.61 to ≤ 6.18.*; unaffected: 7.3.2 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-99309
- https://git.kernel.org/stable/c/bd92e03122f33c159b552867a4abc098d405dfed
- https://git.kernel.org/stable/c/4f238380ea3803afdc815c615521c6f6b13989a3
- https://git.kernel.org/stable/c/d1e92aa651caa352261fb3b78460b7722357835c
- https://git.kernel.org/stable/c/eb96e2a0e817807c48dc8387ca6a5249fdeae3a0