CVE-2026-99291 · Infrastructure
NO FIX YET
The Linux kernel's ksmbd SMB file server writes up to 12 bytes past a 448-byte heap buffer when building an SMB2 CREATE response that includes AAPL (Apple) response contexts. An attacker who can send such requests may corrupt kernel memory.
first public Nov 16, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Only systems running the Linux kernel's ksmbd in-kernel SMB server are exposed, which is off by default and must be enabled. Hosts that do not run ksmbd, or that use Samba instead, can skip it. The sources do not give the affected version ranges.
Not affected if ksmbd-not-enabled, samba-used-instead
Who cares file-server, kernel, ksmbd, linux, smb
uname -r and whether the ksmbd module is loaded with lsmod | grep ksmbdsystemctl status ksmbdUnknown from the sources.
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix SMB2 CREATE response buffer overflow
smb2_allocate_rsp_buf() uses the MAX_CIFS_SMALL_BUFFER_SIZE (448-byte) buffer for a single SMB2_CREATE response. That buffer also holds a 4-byte length field, which only leaves 444 bytes for the SMB2 body.
The AAPL response made this buffer too small. After 8f1b796ff113, a request with AAPL response contexts may need at least 456 bytes. In the 456-byte case, create_aapl_rsp_buf() is appended last, clears 128 bytes, and writes 12 bytes past the allocation.
KASAN reports:
BUG: KASAN: slab-out-of-bounds in create_aapl_rsp_buf+0x31/0x6e0
Write of size 128 at addr ffff88800370954c by task kworker/0:0/9
...
create_aapl_rsp_buf+0x31/0x6e0
smb2_open+0x58f9/0xef10
...
smb2_allocate_rsp_buf+0x19d/0x370
...
The buggy address is located 332 bytes inside of
allocated 448-byte region [ffff888003709400, ffff8880037095c0)
Reserve enough space for any fixed CREATE response KSMBD can build. Store the required allocation size in the per-dialect values table. This keeps the small buffer for other commands and avoids using the max transaction buffer for every CREATE.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.