{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-99380","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2026-09-25T10:25:14.411Z","datePublished":"2026-11-19T14:23:20.787Z","dateUpdated":"2026-11-22T11:07:56.743Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-11-22T11:07:56.743Z"},"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: validate NT transaction response layout and offsets\n\nvalidate_ntransact() assumes that the response uses the fixed 18-word NT\ntransaction layout. A different WordCount makes get_bcc() locate the byte\ncount at a different offset from pSMBr->ByteCount, allowing the subsequent\nbounds checks to use inconsistent response boundaries.\n\nThe function also turns the 32-bit ParameterOffset and DataOffset fields\ninto pointers before checking their bounds. On a 32-bit client, a large\noffset can wrap the pointer below end_of_smb and pass the one-sided pointer\ncomparison. The caller then dereferences the parameter pointer or copies\nfrom the data pointer.\n\nRequire the expected WordCount before reading the byte count. Check each\noffset and count against the received SMB length as integers before forming\neither pointer. Use subtraction after validating the offset so that the\nrange checks cannot overflow."}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H","baseScore":8.1,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:N - The attacker-controlled bytes are the SMB1 NT Transact response (SMB_COM_NT_TRANSACT / NT_TRANSACT_QUERY_SECURITY_DESC): WordCount, ParameterOffset, DataOffset, ParameterCount and DataCount. CIFSSMBGetCIFSACL() receives that PDU on the client TCP session through SendReceive2() and passes rsp_iov to validate_ntransact().\nAC:L - Once a vers=1.0 session exists, the server fills those NT Transact response fields on every QUERY_SECURITY_DESC reply. The 32-bit pointer wrap in validate_ntransact() and a WordCount other than 18 are produced entirely by that reply; there is no race and no hardware state the server cannot set.\nPR:N - The attacker is the SMB1 server on the TCP session the client already opened. CIFSSMBGetCIFSACL() parses the NT Transact response with no capability check on the client; the server does not need an account on the victim.\nUI:R - smb1_operations.get_acl is installed only for an explicit vers=1.0 mount, and CIFSSMBGetCIFSACL() runs only when the client sends NT_TRANSACT_QUERY_SECURITY_DESC. That send comes from cifs_xattr_get() (system.cifs_acl / cifs_ntsd) or from cifs_acl_to_fattr() when the mount has cifsacl or modefromsid. The server cannot push this response unsolicited.\nS:U - validate_ntransact() and the kmemdup() in CIFSSMBGetCIFSACL() run in the client kernel that mounted the share. A bad pointer discloses or oopses that same kernel.\nC:H - On a 32-bit client, validate_ntransact() forms pdata as the SMB base plus the 32-bit DataOffset before the greater-than check against end_of_smb, so a large offset wraps below end_of_smb and is accepted. CIFSSMBGetCIFSACL() then kmemdup()s that range, up to bcc-4 bytes (about 16KB at the default CIFSMaxBufSize), and cifs_xattr_get() copies it to the getxattr caller.\nI:N - CIFSSMBGetCIFSACL() only reads through the parsed pointers: le32_to_cpu(*parm) and kmemdup(pdata, *pbuflen) into a freshly allocated buffer. No store uses ParameterOffset or DataOffset as a destination.\nA:H - If the wrapped parm or data pointer is unmapped, the *parm load or the kmemdup() in CIFSSMBGetCIFSACL() faults and oopses the process that issued the ACL query (getxattr or cifs_acl_to_fattr)."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["fs/smb/client/cifssmb.c"],"versions":[{"version":"0a4b92c05ed02ad7abdd165823eaf4bbcb33ae5c","lessThan":"520b48753e3c54172a078e7e4b82aec83ae2e08d","status":"affected","versionType":"git"},{"version":"0a4b92c05ed02ad7abdd165823eaf4bbcb33ae5c","lessThan":"d55c0c19b0d1f5c0101f9aa3b60534b6d6e11052","status":"affected","versionType":"git"},{"version":"0a4b92c05ed02ad7abdd165823eaf4bbcb33ae5c","lessThan":"83d0d5e0ca22233c75daf139ec0063b9d2ff1ac7","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["fs/smb/client/cifssmb.c"],"versions":[{"version":"2.6.16","status":"affected"},{"version":"0","lessThan":"2.6.16","status":"unaffected","versionType":"semver"},{"version":"6.18.61","lessThanOrEqual":"6.18.*","status":"unaffected","versionType":"semver"},{"version":"7.3.2","lessThanOrEqual":"7.3.*","status":"unaffected","versionType":"semver"},{"version":"7.4-rc1","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"2.6.16","versionEndExcluding":"6.18.61"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"2.6.16","versionEndExcluding":"7.3.2"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"2.6.16","versionEndExcluding":"7.4-rc1"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/520b48753e3c54172a078e7e4b82aec83ae2e08d"},{"url":"https://git.kernel.org/stable/c/d55c0c19b0d1f5c0101f9aa3b60534b6d6e11052"},{"url":"https://git.kernel.org/stable/c/83d0d5e0ca22233c75daf139ec0063b9d2ff1ac7"}],"title":"smb: client: validate NT transaction response layout and offsets","x_generator":{"engine":"bippy-1.2.0"}}}}