* [PATCH] smb: client: fix OOB read/write from unvalidated DataOffset in coalesce_t2()
@ 2026-08-11 19:18 Frank Sorenson
2026-08-12 1:08 ` grayhat
0 siblings, 1 reply; 2+ messages in thread
From: Frank Sorenson @ 2026-08-11 19:18 UTC (permalink / raw)
To: linux-cifs; +Cc: stable, smfrench, grayhat, pc
coalesce_t2() computes data pointers directly from server-supplied
DataOffset fields with no validation against buffer bounds:
data_area_of_tgt = (char *)&pSMBt->hdr.Protocol +
get_unaligned_le16(&pSMBt->t2_rsp.DataOffset);
data_area_of_src = (char *)&pSMBs->hdr.Protocol +
get_unaligned_le16(&pSMBs->t2_rsp.DataOffset);
data_area_of_tgt += total_in_tgt;
...
memcpy(data_area_of_tgt, data_area_of_src, total_in_src);
A small DataOffset can push a pointer below the actual byte area,
overwriting header fields; a large one can push it past the buffer
end, causing out-of-bounds heap reads (source) or writes (target).
The BCC overflow guard does not prevent this: BCC reflects how much
data is present, while DataOffset controls where in the buffer it
starts.
The "validate target area" comment present since the function was
first written in 2005 was a placeholder that was never implemented.
Add lower- and upper-bound checks for both data pointers before the
memcpy, and before any target header fields are modified.
Fixes: e4eb295d38b5 ("[PATCH] cifs: Handle multiple response transact2 part 1 of 2")
Cc: stable@vger.kernel.org
Signed-off-by: Frank Sorenson <sorenson@redhat.com>
---
An independent report with KASAN reproducer (Shen Yongchao,
grayhat@foxmail.com) confirms this vulnerability against v7.2-rc6.
Their proposed fix bounded only the target upper limit; this patch
additionally adds lower-bound checks on both data pointers and
validates the source buffer range.
fs/smb/client/smb1transport.c | 21 ++++++++++++++++++++-
1 file changed, 20 insertions(+), 1 deletion(-)
diff --git a/fs/smb/client/smb1transport.c b/fs/smb/client/smb1transport.c
index 966f2cf83a51..66daa5a37e4a 100644
--- a/fs/smb/client/smb1transport.c
+++ b/fs/smb/client/smb1transport.c
@@ -375,12 +375,31 @@ coalesce_t2(char *second_buf, struct smb_hdr *target_hdr, unsigned int *pdu_len)
data_area_of_tgt = (char *)&pSMBt->hdr.Protocol +
get_unaligned_le16(&pSMBt->t2_rsp.DataOffset);
- /* validate target area */
data_area_of_src = (char *)&pSMBs->hdr.Protocol +
get_unaligned_le16(&pSMBs->t2_rsp.DataOffset);
data_area_of_tgt += total_in_tgt;
+ /*
+ * DataOffset fields are server-supplied and not validated against
+ * buffer bounds; check both data pointers before mutating the
+ * target header.
+ */
+ if (data_area_of_tgt < (char *)target_hdr +
+ sizeof(struct smb_t2_rsp) + sizeof(__le16) ||
+ data_area_of_tgt + total_in_src >
+ (char *)target_hdr + CIFSMaxBufSize + MAX_CIFS_HDR_SIZE) {
+ cifs_dbg(VFS, "%s: target data area out of bounds\n", __func__);
+ return -EPROTO;
+ }
+ if (data_area_of_src < second_buf +
+ sizeof(struct smb_t2_rsp) + sizeof(__le16) ||
+ data_area_of_src + total_in_src >
+ second_buf + smbCalcSize((struct smb_hdr *)second_buf)) {
+ cifs_dbg(VFS, "%s: secondary data area out of bounds\n", __func__);
+ return -EPROTO;
+ }
+
total_in_tgt += total_in_src;
/* is the result too big for the field? */
if (total_in_tgt > USHRT_MAX) {
--
2.55.0
^ permalink raw reply related [flat|nested] 2+ messages in thread* Re: [PATCH] smb: client: fix OOB read/write from unvalidated DataOffset in coalesce_t2()
2026-08-11 19:18 [PATCH] smb: client: fix OOB read/write from unvalidated DataOffset in coalesce_t2() Frank Sorenson
@ 2026-08-12 1:08 ` grayhat
0 siblings, 0 replies; 2+ messages in thread
From: grayhat @ 2026-08-12 1:08 UTC (permalink / raw)
To: Frank Sorenson, linux-cifs; +Cc: stable, smfrench, pc
On Tue, 11 Aug 2026 14:18:46 -0500, Frank Sorenson wrote:
> [PATCH] smb: client: fix OOB read/write from unvalidated DataOffset in coalesce_t2()
Thanks, Frank - this looks good to me. The lower-bound checks on
both pointers and the source range validation cover the cases my
simpler upper-bound-only patch missed, and the Fixes: tag to
e4eb295d38b5 confirms the pre-2012 origin we suspected.
One request: the credit currently sits below the --- line, so it
would be dropped when the patch is applied. Could you add a
Reported-by: Shen Yongchao <grayhat@foxmail.com>
trailer to the commit message proper?
Shen Yongchao
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-08-12 1:08 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-08-11 19:18 [PATCH] smb: client: fix OOB read/write from unvalidated DataOffset in coalesce_t2() Frank Sorenson
2026-08-12 1:08 ` grayhat
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox