{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.3.3-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "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.",
  "id": "DEBIAN-CVE-2026-99291",
  "modified": "2026-11-17T04:47:43.251910432Z",
  "published": "2026-11-16T10:17:01.393Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-99291"
    }
  ],
  "upstream": [
    "CVE-2026-99291"
  ]
}