CVE-2026-99114 json
ksmbd: initialize FileSystemControlFlags in FS_CONTROL_INFORMATION
published 14d ago modified 12d ago also EUVD-2026-112014
- 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: 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.
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-99114
- kernel Azure Linux 3.0 6.6.161.1-1
azure linux advisories AZL-111209
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/995456b5e703e128904a6cbc8b3347eb3d04c72c commit
- git.kernel.org/stable/c/c78aea8984c84767e87f677477e4784deb8adfde commit
- git.kernel.org/stable/c/e8b82184a1982894820a91a72ac9857ddd5dffbf commit
- git.kernel.org/stable/c/370459776468fc68c97008360108f381e3120953 commit
- git.kernel.org/stable/c/d8c450ad0d08980b39b08d435efa921086c8b227 commit
- git.kernel.org/stable/c/03bb4338c3a7c3fc4decf699a35753f0891aab2a commit
- git.kernel.org/stable/c/c0cd3fc6824122014da2b3b0cb7ddeaa2946ec8e commit
Is CVE-2026-99114 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-99114 updated cvss 4.3
kernel: ksmbd: initialize FileSystemControlFlags in FS_CONTROL_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/995456b5e703e128904a6cbc8b3347eb3d04c72c
- git.kernel.org /stable/c/c78aea8984c84767e87f677477e4784deb8adfde
- git.kernel.org /stable/c/e8b82184a1982894820a91a72ac9857ddd5dffbf
- git.kernel.org /stable/c/370459776468fc68c97008360108f381e3120953
- git.kernel.org /stable/c/d8c450ad0d08980b39b08d435efa921086c8b227
- git.kernel.org /stable/c/03bb4338c3a7c3fc4decf699a35753f0891aab2a
- git.kernel.org /stable/c/c0cd3fc6824122014da2b3b0cb7ddeaa2946ec8e
Sources
- CVE List CVE-2026-99114
- NVD CVE-2026-99114
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.