CVE-2026-99115ksmbd: fill in FileSysIdentifier in FS_POSIX_INFORMATION
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fill in FileSysIdentifier in FS_POSIX_INFORMATION smb2_get_info_filesystem() reports 56 bytes for FS_POSIX_INFORMATION, that is the whole of FILE_SYSTEM_POSIX_INFO, but never assigns FileSysIdentifier. Those eight 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. Report the file system id statfs() returned, which is what the field is for. FileSysIdentifier is __le64 and f_fsid is a pair of ints, so assemble the value first, val[0] as the low half, and convert it on the way out.
Timeline
ID reserved
By Linux
- 33 days later
· 33 days later
Published
- 2 days later
· 2 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 93% of all CVEs (12 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < cb9fbcaf1f3351bea771eec557fc6c4d2f35762b
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 1d644ab9eac767d52c9b8dc0eb68c0085994d9b6
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < da2ec27fdd7effbe4c94ec15b6c6a281800c5123
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < f5c50f69a70fe22c44a50c869c8cd65fc35a0686
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < beba2ef6f66a71f20531ac70a1acb0b221e362e9
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < ab057f271ef60ff8163818badc3de75c480eca07
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < db2267b27c054a6c2151ff7fbb67927e784f31d6
- affected 5.15
- unaffected < 5.15
- unaffected 5.15.224 – ≤ 5.15.*
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.161 – ≤ 6.6.*
- unaffected 6.12.115 – ≤ 6.12.*
- unaffected 6.18.59 – ≤ 6.18.*
- unaffected 7.2.13 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References7
- https://git.kernel.org/stable/c/cb9fbcaf1f3351bea771eec557fc6c4d2f35762b (opens in a new tab)
- https://git.kernel.org/stable/c/1d644ab9eac767d52c9b8dc0eb68c0085994d9b6 (opens in a new tab)
- https://git.kernel.org/stable/c/da2ec27fdd7effbe4c94ec15b6c6a281800c5123 (opens in a new tab)
- https://git.kernel.org/stable/c/f5c50f69a70fe22c44a50c869c8cd65fc35a0686 (opens in a new tab)
- https://git.kernel.org/stable/c/beba2ef6f66a71f20531ac70a1acb0b221e362e9 (opens in a new tab)
- https://git.kernel.org/stable/c/ab057f271ef60ff8163818badc3de75c480eca07 (opens in a new tab)
- https://git.kernel.org/stable/c/db2267b27c054a6c2151ff7fbb67927e784f31d6 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-112015 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-99115)Record last updated .