---
id: "CVE-2026-99291"
page: "https://infrastack.ai/live/CVE-2026-99291"
kind: "vulnerability"
aliases: ["CVE-2026-99291"]
title: "Linux ksmbd: SMB2 CREATE response overflows buffer, writing past allocation"
severity: "unknown"
cvss: null
epss: 0.00214
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["file-server", "infrastructure", "kernel", "ksmbd", "linux", "smb"]
not_affected_if: ["ksmbd-not-enabled", "samba-used-instead"]
published_at: "2026-11-16T10:17:01+00:00"
first_seen_at: "2026-11-16T10:39:25+00:00"
updated_at: "2026-11-16T18:53:18+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99291", "first_seen_at": "2026-11-16T10:39:25+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-99291", "first_seen_at": "2026-11-16T18:53:18+00:00"}]
exploit_sources: [{"type": "epss", "score": 0.00214, "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-99291"}]
---

# Linux ksmbd: SMB2 CREATE response overflows buffer, writing past allocation

Link for people: https://infrastack.ai/live/CVE-2026-99291 (this .md is for agents)

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.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the kernel version with `uname -r` and whether the ksmbd module is loaded with `lsmod | grep ksmbd`
- Check whether the SMB server is enabled, for example `systemctl status ksmbd`
- Compare the kernel against the fixed version in the kernel stable tree, unknown from the sources

## Timeline

- 2026-11-16T10:39:25+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-99291
- 2026-11-16T18:53:18+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-99291

## 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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_
