PT-2026-151563
CVE-2026-99382
·
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 FIND data areas that run past the received response
CIFSFindFirst() and CIFSFindNext() take the directory entries of a
TRANS2 FIND FIRST2 or TRANS2 FIND NEXT2 response from DataOffset for
DataCount bytes. validate t2() bounds DataOffset at 1024 and
ParameterCount + DataCount by the byte count, and nothing compares
DataOffset + DataCount with the number of bytes SendReceive() copied
into the buffer.
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 whose data area extends past its end has
srch entries start point at bytes of the request that was just sent,
or at whatever the allocation held before, and those bytes are parsed
as directory entries. cifs readdir() and find cifs entry() walk the
entries with nxt dir entry(), which checks every entry but the first
of a response against the end of the SMB; cifs query path info() and
cifs backup query path info() read the first entry with no check at
all. Those reads stay inside the allocation, but what they return is
not part of the response. The last entry, which LastNameOffset locates
relative to the data area, is bounded against the received response
by an earlier patch of this series, as is every entry that
cifs fill dirent() parses; the walk itself and the two query functions
are not.
SMB1 is not negotiated by default; reaching this code requires an
explicit vers=1.0 mount.
Reject a response whose data area extends past the received length,
with the -EINVAL that validate t2() returns for the other malformed
transaction responses. cifs query path info() and
cifs backup query path info() still read a whole entry from a data
area that may be smaller than one; that is not changed here.
A conforming server is not affected. The data block of a transaction
response is part of the SMB, so DataOffset + DataCount cannot exceed
the smbCalcSize() bytes that SendReceive() copies; coalesce t2()
appends each secondary response to the data area and adds its length
to both DataCount and the byte count, which keeps that relation.
Found an issue in the description? Have something to add? Feel free to write us 👾