{"api_version":"1","generated_at":"2026-10-28T17:00:33+00:00","cve":"CVE-2026-99114","urls":{"html":"https://cve.report/CVE-2026-99114","api":"https://cve.report/api/cve/CVE-2026-99114.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-99114","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-99114"},"summary":{"title":"ksmbd: initialize FileSystemControlFlags in FS_CONTROL_INFORMATION","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: initialize FileSystemControlFlags in FS_CONTROL_INFORMATION\n\nsmb2_get_info_filesystem() reports 48 bytes for FS_CONTROL_INFORMATION,\nthat is the whole of struct smb2_fs_control_info, but never assigns\nFileSystemControlFlags.  Those four bytes go to the client as they are\nfound in the response buffer.\n\nThe buffer is zeroed on allocation, so a standalone request leaks\nnothing.  A compound request can leak: the offset of the next response\nis advanced by the length pinned for the previous one, so a reply that\nwas written into the buffer and then dropped in favour of the short\nerror response of smb2_set_err_rsp() stays there, and the next reply is\nlaid over it with only the header cleared.\n\nksmbd does not implement quota tracking, so report no control flags.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-10-28 11:17:30","updated_at":"2026-10-28 11:17:30"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/d8c450ad0d08980b39b08d435efa921086c8b227","name":"https://git.kernel.org/stable/c/d8c450ad0d08980b39b08d435efa921086c8b227","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/03bb4338c3a7c3fc4decf699a35753f0891aab2a","name":"https://git.kernel.org/stable/c/03bb4338c3a7c3fc4decf699a35753f0891aab2a","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/c0cd3fc6824122014da2b3b0cb7ddeaa2946ec8e","name":"https://git.kernel.org/stable/c/c0cd3fc6824122014da2b3b0cb7ddeaa2946ec8e","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-99114","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99114","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 d8c450ad0d08980b39b08d435efa921086c8b227 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 03bb4338c3a7c3fc4decf699a35753f0891aab2a git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 c0cd3fc6824122014da2b3b0cb7ddeaa2946ec8e git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5.15","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.15 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.59 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.13 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["fs/smb/server/smb2pdu.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"d8c450ad0d08980b39b08d435efa921086c8b227","status":"affected","version":"e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9","versionType":"git"},{"lessThan":"03bb4338c3a7c3fc4decf699a35753f0891aab2a","status":"affected","version":"e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9","versionType":"git"},{"lessThan":"c0cd3fc6824122014da2b3b0cb7ddeaa2946ec8e","status":"affected","version":"e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/smb/server/smb2pdu.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"5.15"},{"lessThan":"5.15","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.59","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.13","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.59","versionStartIncluding":"5.15","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.13","versionStartIncluding":"5.15","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3","versionStartIncluding":"5.15","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: initialize FileSystemControlFlags in FS_CONTROL_INFORMATION\n\nsmb2_get_info_filesystem() reports 48 bytes for FS_CONTROL_INFORMATION,\nthat is the whole of struct smb2_fs_control_info, but never assigns\nFileSystemControlFlags.  Those four bytes go to the client as they are\nfound in the response buffer.\n\nThe buffer is zeroed on allocation, so a standalone request leaks\nnothing.  A compound request can leak: the offset of the next response\nis advanced by the length pinned for the previous one, so a reply that\nwas written into the buffer and then dropped in favour of the short\nerror response of smb2_set_err_rsp() stays there, and the next reply is\nlaid over it with only the header cleared.\n\nksmbd does not implement quota tracking, so report no control flags."}],"providerMetadata":{"dateUpdated":"2026-10-28T10:34:31.576Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/d8c450ad0d08980b39b08d435efa921086c8b227"},{"url":"https://git.kernel.org/stable/c/03bb4338c3a7c3fc4decf699a35753f0891aab2a"},{"url":"https://git.kernel.org/stable/c/c0cd3fc6824122014da2b3b0cb7ddeaa2946ec8e"}],"title":"ksmbd: initialize FileSystemControlFlags in FS_CONTROL_INFORMATION","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-99114","datePublished":"2026-10-28T10:34:31.576Z","dateReserved":"2026-09-25T10:25:14.392Z","dateUpdated":"2026-10-28T10:34:31.576Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-10-28 11:17:30","lastModifiedDate":"2026-10-28 11:17:30","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"99114","Ordinal":"1","Title":"ksmbd: initialize FileSystemControlFlags in FS_CONTROL_INFORMATI","CVE":"CVE-2026-99114","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"99114","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: initialize FileSystemControlFlags in FS_CONTROL_INFORMATION\n\nsmb2_get_info_filesystem() reports 48 bytes for FS_CONTROL_INFORMATION,\nthat is the whole of struct smb2_fs_control_info, but never assigns\nFileSystemControlFlags.  Those four bytes go to the client as they are\nfound in the response buffer.\n\nThe buffer is zeroed on allocation, so a standalone request leaks\nnothing.  A compound request can leak: the offset of the next response\nis advanced by the length pinned for the previous one, so a reply that\nwas written into the buffer and then dropped in favour of the short\nerror response of smb2_set_err_rsp() stays there, and the next reply is\nlaid over it with only the header cleared.\n\nksmbd does not implement quota tracking, so report no control flags.","Type":"Description","Title":"ksmbd: initialize FileSystemControlFlags in FS_CONTROL_INFORMATI"}]}}}