CVE-2026-99083 json
ksmbd: fix heap out-of-bounds write in krb5_authenticate()
published 19d ago modified 12d ago also EUVD-2026-108934
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 39%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix heap out-of-bounds write in krb5_authenticate()
In krb5_authenticate(), out_len is calculated to determine available headroom in response_buf for the incoming Kerberos AP-REP token. However, when SMB2_SESSION_SETUP is processed as a non-first element of a compounded SMB2 request, the calculation omits work->next_smb2_rsp_hdr_off.
This causes out_len to overstate remaining buffer headroom by the cumulative size of prior responses in the compound chain. Consequently, the length check in ksmbd_krb5_authenticate() (*out_len <= resp->spnego_blob_len) passes erroneously, allowing memcpy() to write the AP-REP blob past the end of response_buf into adjacent kernel heap memory.
Fix this by subtracting work->next_smb2_rsp_hdr_off when computing out_len, ensuring it accurately reflects physical remaining buffer space.
Patch / fix
- Linux Linux 5.15.224, 6.1.191, 6.5, 7.3
- linux Debian 13 6.12.115-2
- linux Debian 14 7.2.12-1
debian advisories DEBIAN-CVE-2026-99083
- git.kernel.org/stable/c/a07dfb33112a42437f9d2d0bfd35c68575257381 commit
- git.kernel.org/stable/c/1f73a6d40f4d1bae4f3491c0ec1ea8ee6ce035ff commit
- git.kernel.org/stable/c/59c6dcc5dd9dafe764ca0d40525933b2be69b059 commit
- git.kernel.org/stable/c/80af1bde97d5a85ad6f2c40ca894ccc8fa75a27a commit
- git.kernel.org/stable/c/517404e157395d0f8da125ca956c566895dfcd06 commit
- git.kernel.org/stable/c/4722d06b2907585074252061b1024a696c1cfc23 commit
- git.kernel.org/stable/c/23a0be6a84a38ac169eeab49017934e8e27c65f0 commit
Is CVE-2026-99083 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor 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-99083 updated cvss 9.8
kernel: ksmbd: fix heap out-of-bounds write in krb5_authenticate()
-
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 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9not affected: vulnerable code not present
+1 more productsfewer
Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9
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.45% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/a07dfb33112a42437f9d2d0bfd35c68575257381
- git.kernel.org /stable/c/1f73a6d40f4d1bae4f3491c0ec1ea8ee6ce035ff
- git.kernel.org /stable/c/59c6dcc5dd9dafe764ca0d40525933b2be69b059
- git.kernel.org /stable/c/80af1bde97d5a85ad6f2c40ca894ccc8fa75a27a
- git.kernel.org /stable/c/517404e157395d0f8da125ca956c566895dfcd06
- git.kernel.org /stable/c/4722d06b2907585074252061b1024a696c1cfc23
- git.kernel.org /stable/c/23a0be6a84a38ac169eeab49017934e8e27c65f0
Sources
- CVE List CVE-2026-99083
- NVD CVE-2026-99083
Fencer Intel 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.