CVE-2026-99115: Linux kernel · ksmbd: fill in FileSysIdentifier in FS_POSIX_INFORMATION
Source GCVE Database
Not known to be exploited · fixed in db2267b27c054a6c2151ff7fbb67927e784f31d6 : update Linux kernel when convenient.
Data as of 28 Oct 2026, 14:15 UTC
Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD
- Patch
- Available – fixed in db2267b27c054a6c2151ff7fbb67927e784f31d6, beba2ef6f66a71f20531ac70a1acb0b221e362e9, ab057f271ef60ff8163818badc3de75c480eca07
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.
What to do
Upgrade Linux kernel to db2267b27c054a6c2151ff7fbb67927e784f31d6, beba2ef6f66a71f20531ac70a1acb0b221e362e9 or ab057f271ef60ff8163818badc3de75c480eca07.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix has been implemented in the Linux kernel to correctly populate the FileSysIdentifier field in FS_POSIX_INFORMATION responses. Users should apply the official kernel updates that include this patch once available. Until then, no specific workaround is documented. Monitor vendor advisories for patch availability.
Description
A vulnerability in the Linux kernel's ksmbd component involves the FS_POSIX_INFORMATION structure where the FileSysIdentifier field is not properly assigned in smb2_get_info_filesystem(). This can cause residual data from previous responses to be leaked to clients during compound SMB2 requests. The issue arises because the response buffer is reused without clearing the FileSysIdentifier field, potentially exposing unintended data. The fix involves correctly reporting the file system ID as returned by statfs().
References
- nvd.nist.gov/vuln/detail/CVE-2026-99115 (opens in a new tab)
- git.kernel.org/stable/c/ab057f271ef60ff8163818badc3de75c480eca07 (opens in a new tab)
- git.kernel.org/stable/c/beba2ef6f66a71f20531ac70a1acb0b221e362e9 (opens in a new tab)
- git.kernel.org/stable/c/db2267b27c054a6c2151ff7fbb67927e784f31d6 (opens in a new tab)