CVE-2026-43185 in the critical feed json
ksmbd: fix signededness bug in smb_direct_prepare_negotiation()
published 2026-05-06 6 mo ago modified 2026-10-30 10 d ago also EUVD-2026-27748
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 59%
- public exploits
- 0
- none known
Summary
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)
Patch / fix
- Linux Linux 6.1.191, 6.6.160, 6.12.114, 6.18.16, 6.19.6, 7.0
- linux Debian 13 6.12.115-2
- linux Debian 14 6.19.6-1
debian advisories DEBIAN-CVE-2026-43185
- linux Ubuntu 22.04 LTS 5.15.0-185.195
- linux Ubuntu 24.04 LTS 6.8.0-134.134
- linux-aws Ubuntu 22.04 LTS 5.15.0-1111.118
- linux-aws Ubuntu 24.04 LTS 6.8.0-1060.63
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1111.121
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1063.69
- linux-gke Ubuntu 22.04 LTS 5.15.0-1107.113
- linux-gke Ubuntu 24.04 LTS 6.8.0-1058.64
ubuntu advisories UBUNTU-CVE-2026-43185
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/1c268fd2f59dc9ccb2c2a7d1f439b232dbe1c06c commit
- git.kernel.org/stable/c/56eab82fa6fb5ca024b0514e249d40d9b23ee5a7 commit
- git.kernel.org/stable/c/a110dbe928561d440e9e117d17331139a0bedace commit
- git.kernel.org/stable/c/ceae058eb707ddd0d68f0872f9d9f23b7c30c37b commit
- git.kernel.org/stable/c/55abc475d096da4a5356b6efb0cfdc6156bc1550 commit
- git.kernel.org/stable/c/6b4f875aac344cdd52a1f34cc70ed2f874a65757 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-43185 updated
kernel: ksmbd: fix signededness bug in smb_direct_prepare_negotiation()
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.89% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-674 Uncontrolled Recursion
- Technology feeds
References
- git.kernel.org /stable/c/1c268fd2f59dc9ccb2c2a7d1f439b232dbe1c06c
- git.kernel.org /stable/c/56eab82fa6fb5ca024b0514e249d40d9b23ee5a7
- git.kernel.org /stable/c/a110dbe928561d440e9e117d17331139a0bedace
-
git.kernel.org
/stable/c/ceae058eb707ddd0d68f0872f9d9f23b7c30c37b
patch
-
git.kernel.org
/stable/c/55abc475d096da4a5356b6efb0cfdc6156bc1550
patch
-
git.kernel.org
/stable/c/6b4f875aac344cdd52a1f34cc70ed2f874a65757
patch
Sources
- CVE List CVE-2026-43185
- NVD CVE-2026-43185
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.