diff options
| author | Frank Sorenson <sorenson@redhat.com> | 2026-09-16 16:34:00 -0500 |
|---|---|---|
| committer | Paulo Alcantara <pc@manguebit.org> | 2026-09-17 15:04:26 -0300 |
| commit | 5f0306e731e2f46e91419eae57eee3a241c055e0 (patch) | |
| tree | 62625befaa583caf0bd6aaed2344182ee9757a71 /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | 4775c3b7a597907e0b97556c7986fda238a377ae (diff) | |
| download | linux-next-5f0306e731e2f46e91419eae57eee3a241c055e0.tar.gz linux-next-5f0306e731e2f46e91419eae57eee3a241c055e0.zip | |
smb: client: fix reparse buffer bounds in cifs_query_reparse_point()
In cifs_query_reparse_point(), the start >= end check before casting to
struct reparse_data_buffer * only ensures the start pointer is within the
response. It fails to verify that there is enough space remaining for the
fixed 8-byte header of the structure.
If a server provides a DataOffset that leaves less than 8 bytes remaining,
the check passes, but subsequent reads of ReparseTag and ReparseDataLength
will occur out-of-bounds.
Fix this by ensuring the remaining space is at least the size of the
reparse_data_buffer structure before accessing its fields.
Fixes: 56e84c64fc25 ("cifs: Fix validation of SMB1 query reparse point response")
Cc: stable@vger.kernel.org
Signed-off-by: Frank Sorenson <sorenson@redhat.com>
Reviewed-by: David Howells <dhowells@redhat.com>
Signed-off-by: Paulo Alcantara <pc@manguebit.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions
