Skip to main content
Menu
CVEs

CVE

Linux kernel buffer overflow in ksmbd SMB2 CREATE responses

CVE-2026-99291EUVD-2026-126197GHSA-PHXC-WW8F-9C6W

Exploited
No known exploitation
Fix
Fixed in 7.3
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 7.3.

Published
Last modified
Reference
Last checked
0.21% · 11th percentile
20/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

The ksmbd server in the Linux kernel has a buffer overflow in how it builds responses to SMB2 CREATE requests, which can write past the end of a memory buffer. The overflow happens when a request includes AAPL response contexts, because the buffer is too small for the response.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

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.

cve.now Index

20Pcve.now Index 20 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
  • Severity?/10Unknown. No CVSS score or vendor rating
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 42 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 7.3.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-99291 (ksmbd: fix SMB2 CREATE response buffer overflow), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-99291 (entry last updated 2026-11-16):
Affected:
- Linux Linux: from 7.2.6, fixed in 7.3
- Linux Linux: versions 7.3
Fixed versions: 7.3.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99291 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99291 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/824a572c0f909ca51fdb7e18e4eee33ca7896c7a
- https://git.kernel.org/stable/c/713c31a3a225b6239a37ac7fbfb394567f8b3519
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-99291
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99291"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • Linux Linux

    From 7.2.6 · fixed in 7.3

  • Linux Linux

    7.3

Evidence 4

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 2

  1. Link
  2. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-99291

Is CVE-2026-99291 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-99291?

Linux: from 7.2.6 before 7.3. Linux: version 7.3.Source: cve.now feed data

How do I fix CVE-2026-99291?

Upgrade to a fixed version: 7.3.Source: cve.now feed data