CVE-2026-99273
ksmbd: reserve space for the UTF-16 terminator in stream info
No known exploitation. No EPSS score yet. Fixed versions are out.
No public exploit knownFix1 product4 fixed builds listed below
No ready-made check. Neither Nuclei nor OpenVAS has one for this CVE yet.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 06a751809ebd33e95b05bf733697318a17a4872bUpgrade to: 06a751809ebd33e95b05bf733697318a17a4872bAffected: ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 0e64f89563164719ceb1aa33f2a8bfd6391fa340Upgrade to: 0e64f89563164719ceb1aa33f2a8bfd6391fa340Affected: ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < a025c4991a7d83edc4dd339e3ea86d8ff6226ecaUpgrade to: a025c4991a7d83edc4dd339e3ea86d8ff6226ecaAffected: < 6.18.61Upgrade to: 6.18.61 + 1 more branchStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
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.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
No EPSS score yet. New CVEs are usually scored within a few days.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI