CVE-2026-99115 json
ksmbd: fill in FileSysIdentifier in FS_POSIX_INFORMATION
published 14d ago modified 12d ago also EUVD-2026-112015
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 7.3
- linux Debian 13 6.12.115-2
- linux Debian 14 7.2.13-1
debian advisories DEBIAN-CVE-2026-99115
- kernel Azure Linux 3.0 6.6.161.1-1
azure linux advisories AZL-111212
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/cb9fbcaf1f3351bea771eec557fc6c4d2f35762b commit
- git.kernel.org/stable/c/1d644ab9eac767d52c9b8dc0eb68c0085994d9b6 commit
- git.kernel.org/stable/c/da2ec27fdd7effbe4c94ec15b6c6a281800c5123 commit
- git.kernel.org/stable/c/f5c50f69a70fe22c44a50c869c8cd65fc35a0686 commit
- git.kernel.org/stable/c/beba2ef6f66a71f20531ac70a1acb0b221e362e9 commit
- git.kernel.org/stable/c/ab057f271ef60ff8163818badc3de75c480eca07 commit
- git.kernel.org/stable/c/db2267b27c054a6c2151ff7fbb67927e784f31d6 commit
Is CVE-2026-99115 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-99115 updated cvss 4.3
kernel: ksmbd: fill in FileSysIdentifier in FS_POSIX_INFORMATION
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9not affected: vulnerable code not present
+1 more productsfewer
Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/cb9fbcaf1f3351bea771eec557fc6c4d2f35762b
- git.kernel.org /stable/c/1d644ab9eac767d52c9b8dc0eb68c0085994d9b6
- git.kernel.org /stable/c/da2ec27fdd7effbe4c94ec15b6c6a281800c5123
- git.kernel.org /stable/c/f5c50f69a70fe22c44a50c869c8cd65fc35a0686
- git.kernel.org /stable/c/beba2ef6f66a71f20531ac70a1acb0b221e362e9
- git.kernel.org /stable/c/ab057f271ef60ff8163818badc3de75c480eca07
- git.kernel.org /stable/c/db2267b27c054a6c2151ff7fbb67927e784f31d6
Sources
- CVE List CVE-2026-99115
- NVD CVE-2026-99115
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.