Koffei

CVE-2026-99273

🟠 Medium

Linux kernel. The record carries no CWE from any container and no SSVC decision, and its only references are git.kernel.org stable commits, which are patches rather than advisories, so there is nothing to cite beyond the commit itself, here the ksmbd SMB server. ksmbd is not built by default on most distributions, which is relevant to whether this applies at all · Before 6.18.61 and before 7.3.2 on their stable branches ; the original fix is in 7.4-rc1

CVSS (Koffei note)
–
EPSS (2026-11-18)
0.157%
4.89th percentile

Exploitation

No — no exploitation reported, no SSVC container and no CVSS, so this row has no severity signal from any party other than EPSS. Neither CISA KEV nor its JSON feed could be reached in this run, so KEV status comes from the record's CISA-ADP container. Existing PoC (not opened), recorded from the proof-of-concept list supplied on 09/11/2026. Rated 🟠 on the public proof of concept, and the row is deliberately explicit that a two-byte overflow in a non-default component with EPSS in the 4th percentile is at the bottom of any reasonable queue

Timeline

  1. 07/11/2026CVE record published (CVE List)

Risk

CVSS n/d — the record carries no CVSS score and no CWE from any container. EPSS 0.155% (4.66th percentile, scored 08/11/2026), the lowest of any row added in this batch (the description: ksmbd, the in-kernel SMB server, does not reserve room for the UTF-16 terminator when building stream info responses, so a full 448-byte buffer is written two bytes past its end. The fix adds one extra UTF-16 unit to both size checks and leaves reported lengths unchanged)

Fix

Yes — 6.18.61 or 7.3.2

Official description

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.