PT-2026-151562
CVE-2026-99381
·
Published
2026-11-19
·
Updated
2026-11-19
Description by
Score
N/A
Not availableNo severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
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 TRANS2 FIND FIRST2 or
TRANS2 FIND NEXT2 response at ParameterOffset. validate t2() 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. smb init() places the
request and the response in the same cifs request allocation and
cifs buf get() 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 FIND NEXT2 or
FIND CLOSE2, 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 smb EIO2()
with a new smb eio traces 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 smb EIO2() 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
FIND FIRST2 and 8 bytes for FIND NEXT2, which is what
T2 FFIRST RSP PARMS and T2 FNEXT RSP PARMS hold.
This patch depends on "smb: client: reject FIND data areas that run
past the received response", whose declarations it extends.
Found an issue in the description? Have something to add? Feel free to write us 👾