{"id":"CVE-2026-99113","summary":"ksmbd: zero the FS_OBJECT_ID_INFORMATION buffer before filling it in","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: zero the FS_OBJECT_ID_INFORMATION buffer before filling it in\n\nsmb2_get_info_filesystem() reports 64 bytes for FS_OBJECT_ID_INFORMATION,\nthat is the whole of struct object_id_info, but writes only 46 of them:\n\n - objid[] is 16 bytes, and when the volume UUID is not available only\n   sizeof(stfs.f_fsid) (8) bytes are copied into it;\n - extended_info.version_string[] is STRING_LENGTH (28) bytes, and only\n   strlen(\"1.1.0\") (5) bytes are copied into it.\n\nThe response buffer is zeroed on allocation (kvzalloc() in\nsmb2_allocate_rsp_buf()), so for a standalone request the remaining 31\nbytes are zero.  In a compound request they need not be.  The offset of\nthe next response is advanced by the length pinned for the previous one,\nso if a preceding command wrote its reply into the buffer and then\nfailed, smb2_set_err_rsp() pins only the short error response and the\nnext reply lands inside the area that has already been written.  Only\nthe header is cleared there:\n\n\tmemset((char *)rsp_hdr, 0, sizeof(struct smb2_hdr) + 2);\n\nThe client then receives up to 31 bytes of a response it was not meant\nto see, including one that failed with an access denied error.\n\nClear the structure before filling it in.  As a side effect\nversion_string is now NUL terminated.","modified":"2026-11-01T02:30:18.867957121Z","published":"2026-10-28T10:34:30.767Z","database_specific":{"cna_assigner":"Linux","osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99113.json"},"references":[{"type":"WEB","url":"https://git.kernel.org/stable/c/015fffa48e96ca8d73a627445341ccff86b02251"},{"type":"WEB","url":"https://git.kernel.org/stable/c/1a35a81c302b36fe4acd35b47b51d5d73e89ba0a"},{"type":"WEB","url":"https://git.kernel.org/stable/c/399aa12450a61a5c73dc77e73f069ece9687c95d"},{"type":"WEB","url":"https://git.kernel.org/stable/c/3fc33ac2125b60f103592b83821f69f3f9aa23ba"},{"type":"WEB","url":"https://git.kernel.org/stable/c/898cb4f2e12a5ddea1b2d821cc642c3100f46da7"},{"type":"WEB","url":"https://git.kernel.org/stable/c/90898571fb2c6813c007a62833dd65c00481d44e"},{"type":"WEB","url":"https://git.kernel.org/stable/c/dbd0f13de153d7094b85034daffa7533d7c2b17a"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99113.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99113"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9"},{"fixed":"dbd0f13de153d7094b85034daffa7533d7c2b17a"},{"fixed":"90898571fb2c6813c007a62833dd65c00481d44e"},{"fixed":"1a35a81c302b36fe4acd35b47b51d5d73e89ba0a"},{"fixed":"3fc33ac2125b60f103592b83821f69f3f9aa23ba"},{"fixed":"898cb4f2e12a5ddea1b2d821cc642c3100f46da7"},{"fixed":"015fffa48e96ca8d73a627445341ccff86b02251"},{"fixed":"399aa12450a61a5c73dc77e73f069ece9687c95d"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99113.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.15.0"},{"fixed":"5.15.224"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"6.1.191"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.161"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.115"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.59"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"7.2.13"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99113.json"}}],"schema_version":"1.9.2"}