VulnerabilityPublished 28 Oct 2026

CVE-2026-99114: Linux kernel · ksmbd: initialize FileSystemControlFlags in FS_CONTROL_INFORMATION

Affects Linux kernelSource CVE Database V5

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

Data as of 28 Oct 2026, 10:58 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Patch: Available – fixed in d8c450ad0d08980b39b08d435efa921086c8b227, c0cd3fc6824122014da2b3b0cb7ddeaa2946ec8e, 03bb4338c3a7c3fc4decf699a35753f0891aab2a

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to d8c450ad0d08980b39b08d435efa921086c8b227, c0cd3fc6824122014da2b3b0cb7ddeaa2946ec8e or 03bb4338c3a7c3fc4decf699a35753f0891aab2a.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, < d8c450ad0d08980b39b08d435efa921086c8b227	Fixed in d8c450ad0d08980b39b08d435efa921086c8b227
LinuxLinux	Affected ≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, < c0cd3fc6824122014da2b3b0cb7ddeaa2946ec8e	Fixed in c0cd3fc6824122014da2b3b0cb7ddeaa2946ec8e
LinuxLinux	Affected ≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, < 03bb4338c3a7c3fc4decf699a35753f0891aab2a	Fixed in 03bb4338c3a7c3fc4decf699a35753f0891aab2a
LinuxLinux	Affected =5.15	Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: ksmbd: initialize FileSystemControlFlags in FS_CONTROL_INFORMATION smb2_get_info_filesystem() reports 48 bytes for FS_CONTROL_INFORMATION, that is the whole of struct smb2_fs_control_info, but never assigns FileSystemControlFlags. Those four bytes go to the client as they are found in the response buffer. The buffer is zeroed on allocation, so a standalone request leaks nothing. A compound request can leak: the offset of the next response is advanced by the length pinned for the previous one, so a reply that was written into the buffer and then dropped in favour of the short error response of smb2_set_err_rsp() stays there, and the next reply is laid over it with only the header cleared. ksmbd does not implement quota tracking, so report no control flags.

References

Community reviews

Loading reviews…