CVE-2026-43185: Linux kernel · ksmbd: fix signededness bug in smb_direct_prepare_negotiation()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical · fixed in ceae058eb707ddd0d68f0872f9d9f23b7c30c37b : patch Linux kernel as a priority.
Data as of 26 Oct 2026, 14:18 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in ceae058eb707ddd0d68f0872f9d9f23b7c30c37b, a110dbe928561d440e9e117d17331139a0bedace, 56eab82fa6fb5ca024b0514e249d40d9b23ee5a7 +2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 6 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix signededness bug in smb_direct_prepare_negotiation() smb_direct_prepare_negotiation() casts an unsigned __u32 value from sp->max_recv_size and req->preferred_send_size to a signed int before computing min_t(int, ...). A maliciously provided preferred_send_size of 0x80000000 will return as smaller than max_recv_size, and then be used to set the maximum allowed alowed receive size for the next message. By sending a second message with a large value (>1420 bytes) the attacker can then achieve a heap buffer overflow. This fix replaces min_t(int, ...) with min_t(u32)
References
- git.kernel.org/stable/c/56eab82fa6fb5ca024b0514e249d40d9b23ee5a7 (opens in a new tab)
- git.kernel.org/stable/c/a110dbe928561d440e9e117d17331139a0bedace (opens in a new tab)
- git.kernel.org/stable/c/ceae058eb707ddd0d68f0872f9d9f23b7c30c37b (opens in a new tab)
- git.kernel.org/stable/c/55abc475d096da4a5356b6efb0cfdc6156bc1550 (opens in a new tab)
- git.kernel.org/stable/c/6b4f875aac344cdd52a1f34cc70ed2f874a65757 (opens in a new tab)