CVE-2026-99381: smb: client: reject short or out-of-range FIND response parameters

Published Nov 19, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

smb: client: reject short or out-of-range FIND response parameters

CIFSFindFirst() and CIFSFindNext() read the SearchHandle, SearchCount, EndofSearch and LastNameOffset of a TRANS2FINDFIRST2 or TRANS2FINDNEXT2 response at ParameterOffset. validatet2() bounds the offset at 1024 and ParameterCount below 512, and nothing compares them with the number of bytes SendReceive() copied into the buffer or with the size of the response parameters. smbinit() places the request and the response in the same cifsrequest allocation and cifsbufget() clears only the start of it, so a short response with a ParameterOffset past its end has the search handle, the entry count, the end-of-search flag and the last-entry offset read out of the request that was just sent, or out of whatever the allocation held before, and a ParameterCount smaller than the parameters has them read past the end of the parameter block. The reads stay inside the allocation, but what they return is not part of the response, and CIFSFindFirst() then hands back a search handle the server never sent. That handle is sent back to the server in the next FINDNEXT2 or FINDCLOSE2, so two bytes of the buffer leak at an offset the server picks.

SMB1 is not negotiated by default; reaching this code requires an explicit vers=1.0 mount.

Reject a response whose parameter area is smaller than the response parameters or extends past the received length, returning smbEIO2() with a new smbeiotraces value for each of the two responses, like the other response checks this file gained since v6.19. Backports to trees before v6.19 need smbEIO2() replaced with -EINVAL and the trace.h hunk dropped.

A conforming server is not affected. The parameter block of a transaction response is part of the SMB, so ParameterOffset + ParameterCount cannot exceed the smbCalcSize() bytes that SendReceive() copies, and the response parameters are 10 bytes for FINDFIRST2 and 8 bytes for FINDNEXT2, which is what T2FFIRSTRSPPARMS and T2FNEXTRSPPARMS hold.

This patch depends on "smb: client: reject FIND data areas that run past the received response", whose declarations it extends.

Affected Software

1 affected componentFixes available
linux/kernel>=2.6.12<7.3.2
7.3.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.2

Event History

Nov 19, 2026
CVE Published
via MITRE·02:23 PM
Data Sourced
via MITRE·02:23 PM
Description
Data Sourced
via OSV·02:23 PM
DescriptionAffected Software
Data Sourced
via NVD·03:17 PM
Description

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203