CVE-2026-99565
ksmbd: wait for negotiation before receiving another PDU
Description
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.
INFO
Published Date :
Nov. 19, 2026, 2:45 p.m.
Last Modified :
Nov. 19, 2026, 2:45 p.m.
Remotely Exploit :
No
Source :
Linux
Solution
- Wait for negotiation to complete before reading another PDU.
- Ensure work queued during new connection waits for negotiation.
- Update the Linux kernel to the latest stable version.
- Apply vendor-supplied patches for ksmbd.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-99565 vulnerability anywhere in the article.