{"api_version":"1","generated_at":"2026-10-28T17:00:27+00:00","cve":"CVE-2026-99115","urls":{"html":"https://cve.report/CVE-2026-99115","api":"https://cve.report/api/cve/CVE-2026-99115.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-99115","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-99115"},"summary":{"title":"ksmbd: fill in FileSysIdentifier in FS_POSIX_INFORMATION","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fill in FileSysIdentifier in FS_POSIX_INFORMATION\n\nsmb2_get_info_filesystem() reports 56 bytes for FS_POSIX_INFORMATION,\nthat is the whole of FILE_SYSTEM_POSIX_INFO, but never assigns\nFileSysIdentifier.  Those eight bytes go to the client as they are found\nin 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\nReport the file system id statfs() returned, which is what the field is\nfor.  FileSysIdentifier is __le64 and f_fsid is a pair of ints, so\nassemble the value first, val[0] as the low half, and convert it on the\nway out.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-10-28 11:17:31","updated_at":"2026-10-28 11:17:31"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/db2267b27c054a6c2151ff7fbb67927e784f31d6","name":"https://git.kernel.org/stable/c/db2267b27c054a6c2151ff7fbb67927e784f31d6","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/ab057f271ef60ff8163818badc3de75c480eca07","name":"https://git.kernel.org/stable/c/ab057f271ef60ff8163818badc3de75c480eca07","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/beba2ef6f66a71f20531ac70a1acb0b221e362e9","name":"https://git.kernel.org/stable/c/beba2ef6f66a71f20531ac70a1acb0b221e362e9","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-99115","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99115","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 beba2ef6f66a71f20531ac70a1acb0b221e362e9 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 ab057f271ef60ff8163818badc3de75c480eca07 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 db2267b27c054a6c2151ff7fbb67927e784f31d6 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":"beba2ef6f66a71f20531ac70a1acb0b221e362e9","status":"affected","version":"e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9","versionType":"git"},{"lessThan":"ab057f271ef60ff8163818badc3de75c480eca07","status":"affected","version":"e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9","versionType":"git"},{"lessThan":"db2267b27c054a6c2151ff7fbb67927e784f31d6","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: fill in FileSysIdentifier in FS_POSIX_INFORMATION\n\nsmb2_get_info_filesystem() reports 56 bytes for FS_POSIX_INFORMATION,\nthat is the whole of FILE_SYSTEM_POSIX_INFO, but never assigns\nFileSysIdentifier.  Those eight bytes go to the client as they are found\nin 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\nReport the file system id statfs() returned, which is what the field is\nfor.  FileSysIdentifier is __le64 and f_fsid is a pair of ints, so\nassemble the value first, val[0] as the low half, and convert it on the\nway out."}],"providerMetadata":{"dateUpdated":"2026-10-28T10:34:32.347Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/beba2ef6f66a71f20531ac70a1acb0b221e362e9"},{"url":"https://git.kernel.org/stable/c/ab057f271ef60ff8163818badc3de75c480eca07"},{"url":"https://git.kernel.org/stable/c/db2267b27c054a6c2151ff7fbb67927e784f31d6"}],"title":"ksmbd: fill in FileSysIdentifier in FS_POSIX_INFORMATION","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-99115","datePublished":"2026-10-28T10:34:32.347Z","dateReserved":"2026-09-25T10:25:14.392Z","dateUpdated":"2026-10-28T10:34:32.347Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-10-28 11:17:31","lastModifiedDate":"2026-10-28 11:17:31","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"99115","Ordinal":"1","Title":"ksmbd: fill in FileSysIdentifier in FS_POSIX_INFORMATION","CVE":"CVE-2026-99115","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"99115","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fill in FileSysIdentifier in FS_POSIX_INFORMATION\n\nsmb2_get_info_filesystem() reports 56 bytes for FS_POSIX_INFORMATION,\nthat is the whole of FILE_SYSTEM_POSIX_INFO, but never assigns\nFileSysIdentifier.  Those eight bytes go to the client as they are found\nin 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\nReport the file system id statfs() returned, which is what the field is\nfor.  FileSysIdentifier is __le64 and f_fsid is a pair of ints, so\nassemble the value first, val[0] as the low half, and convert it on the\nway out.","Type":"Description","Title":"ksmbd: fill in FileSysIdentifier in FS_POSIX_INFORMATION"}]}}}