Skip to main content
VulnerabilityPublished

CVE-2026-99273: Linux kernel · ksmbd: reserve space for the UTF-16 terminator in stream info

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in a025c4991a7d83edc4dd339e3ea86d8ff6226eca : update Linux kernel when convenient.

Data as of 7 Nov 2026, 14:20 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in a025c4991a7d83edc4dd339e3ea86d8ff6226eca, 7.3.2, 06a751809ebd33e95b05bf733697318a17a4872b +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • <6.18.61
  • <7.3.2
Fixed in
  • a025c4991a7d83edc4dd339e3ea86d8ff6226eca
  • 7.3.2
  • 06a751809ebd33e95b05bf733697318a17a4872b
  • 6.18.61
  • 0e64f89563164719ceb1aa33f2a8bfd6391fa340

AI-suggested

A fix is available in Linux kernel versions 6.18.61 and 7.3.2 and associated commits. Users and administrators should upgrade to these or later kernel versions to remediate this vulnerability. No additional mitigation steps are indicated.

Description

A vulnerability in the Linux kernel's ksmbd component involves insufficient space allocation for a UTF-16 terminator in stream information. The function smb_strtoUTF16() writes a terminating zero UTF-16 unit after converted characters, but the buffer allocation in get_file_stream_info() does not reserve space for this terminator. This causes the terminator to be written two bytes beyond the allocated buffer when the entry exactly fills the 448-byte small response buffer. The issue has been fixed by reserving one extra UTF-16 unit in the buffer allocation checks. The terminator is not part of the wire format, so reported lengths remain unchanged.

References

Community reviews

Loading reviews…