Skip to main content
Menu
CVEs

Linux kernel out-of-bounds read in ksmbd during SMB negotiation

CVE-2026-99565Published November 19, 2026, updated

Exploited
No known exploitation
Fix
Fixed in 5.16, 6.2, 6.3
Who is exposed
Not reported

Summary

In the Linux kernel, the following vulnerability has been resolved:

ksmbd: wait for negotiation before receiving another PDU

The receive thread queues a request and can read the next PDU before the negotiation worker finishes. While need_neg is set, the next PDU can cause ksmbd_init_smb_server() to replace conn->ops. A pipelined SMB2 request can therefore make the worker handle an earlier, shorter SMB1 request with SMB2 operations and read beyond its buffer.

An SMB1 multi-protocol negotiate may be followed by an SMB2 NEGOTIATE that changes conn->ops again. Wait for work queued while the connection is new or needs negotiation to complete before reading another PDU. This keeps the operations stable for both stages of negotiation without changing when need_neg is cleared.

What to do

Upgrade to a fixed version: 5.16, 6.2, 6.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-99565 (ksmbd: wait for negotiation before receiving another PDU), 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-99565 (entry last updated 2026-11-19):
Affected:
- Linux Linux: from 5.15.145, fixed in 5.16; from 6.1.24, fixed in 6.2; from 6.2.11, fixed in 6.3
- Linux Linux: versions 6.3
Fixed versions: 5.16, 6.2, 6.3.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99565 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99565 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/a9039d6c9de5dfd91f360b085da75899055b15a5
- https://git.kernel.org/stable/c/49675f7bc0e1ae12a60f6af5cb2b800eb39fe055
- https://git.kernel.org/stable/c/aaf8a64a3fbf745eddea729fe27c6e22f4a009e2
- https://git.kernel.org/stable/c/d4a52e78378a501ae38f676e85a60a2a6c21af35
- https://git.kernel.org/stable/c/68f410faedaf6ee74d81e574733c50ebcc1bd8ed
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-99565
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-99565"}.

Affected versions

cve.now Index

20Pof 100 · provisional · methodology v3
  • 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

Timeline

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

Evidence 7

Questions about CVE-2026-99565

Is CVE-2026-99565 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-99565?

Linux: from 5.15.145 before 5.16; from 6.1.24 before 6.2; from 6.2.11 before 6.3. Linux: version 6.3.

Source: cve.now feed data

How do I fix CVE-2026-99565?

Upgrade to a fixed version: 5.16, 6.2, 6.3.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.