CVE-2026-99273: ksmbd: reserve space for the UTF-16 terminator in stream info
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-11 15:49 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
In the Linux kernel, the following vulnerability has been resolved: ksmbd: reserve space for the UTF-16 terminator in stream info smb_strtoUTF16() always writes a terminating zero UTF-16 unit after the converted characters, but get_file_stream_info() budgets only sizeof(struct smb2_file_stream_info) + streamlen * 2 for a stream entry and sizeof(struct smb2_file_stream_info) + 7 * 2 for the trailing “::$DATA” entry. When an entry exactly fills the 448-byte small response buffer, the terminator is written two bytes past the allocation. Reserve one extra UTF-16 unit in both budget checks. The terminator is not part of the wire format, so the reported lengths are unchanged.
Description quoted from the CVE record (assigned by Linux, published 2026-11-07).
How it can be exploited
Public exploit evidence (Exploit Observer)
Exploit Observer found 1 code repository naming this CVE.
Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.
See all 5 references on Exploit Observer
Live scores
- EPSS
- 0.002
low predicted chance of attack - VEDAS
- 0.978
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| Linux | from 1da177e4c3f4 before 583ede545a14 (git commit) from 1da177e4c3f4 before 06a751809ebd (git commit) from 1da177e4c3f4 before 0e64f8956316 (git commit) from 1da177e4c3f4 before a025c4991a7d (git commit) before 6.12.117 before 6.18.61 before 7.3.2 | Not stated |
| Linux | Not stated | 6.12.117 is not affected; 6.18.61 is not affected; 7.3.2 is not affected; 7.4-rc1 is not affected |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
Fixed versions stated in the CVE record: 6.12.117, 6.18.61, 7.3.2.
How to detect it
There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.
References
Other references
- https://git.kernel.org/stable/c/583ede545a14f275a959772b5e1e50fe3e14b861
- https://git.kernel.org/stable/c/06a751809ebd33e95b05bf733697318a17a4872b
- https://git.kernel.org/stable/c/0e64f89563164719ceb1aa33f2a8bfd6391fa340
- https://git.kernel.org/stable/c/a025c4991a7d83edc4dd339e3ea86d8ff6226eca
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners
