CVE Feed
— Unscored

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix SMB2 CREATE response buffer overflow smb2allocaterspbuf()…

CVE-2026-99291

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix SMB2 CREATE response buffer overflow smb2allocaterspbuf() uses the MAXCIFSSMALLBUFFERSIZE (448-byte) buffer for a single SMB2CREATE 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, createaaplrspbuf() is appended last, clears 128 bytes, and writes 12 bytes past the allocation. KASAN reports: BUG: KASAN: slab-out-of-bounds in createaaplrspbuf+0x31/0x6e0 Write of size 128 at addr ffff88800370954c by task kworker/0:0/9 ... createaaplrspbuf+0x31/0x6e0 smb2open+0x58f9/0xef10 ... smb2allocaterspbuf+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.

Assessment

CVSS
Not yet scored
Severity
Unscored
Known exploited
Not listed in CISA KEV
Exploit availability
Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published
16 November 2026
Last updated
16 November 2026
Affected
Linux · Linux
Assigner
Linux

At the source

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept
Before you submit *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-99291