public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Dan Carpenter <error27@gmail.com>
To: Delene Tchio Romuald <delenetchior1@gmail.com>
Cc: gregkh@linuxfoundation.org,
	Ethan Tidmore <ethantidmore06@gmail.com>,
	Sam Daly <sam@samdaly.ie>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/5] staging: rtl8723bs: fix heap buffer overflow in recvframe_defrag()
Date: Wed, 15 Apr 2026 19:10:47 +0300	[thread overview]
Message-ID: <ad-4h1qvjR_pki_v@stanley.mountain> (raw)
In-Reply-To: <ad-tmii6T23d-kZT@stanley.mountain>

On Wed, Apr 15, 2026 at 06:24:10PM +0300, Dan Carpenter wrote:
> > diff --git a/drivers/staging/rtl8723bs/core/rtw_recv.c b/drivers/staging/rtl8723bs/core/rtw_recv.c
> > index f78194d508dfc..717e0594d983a 100644
> > --- a/drivers/staging/rtl8723bs/core/rtw_recv.c
> > +++ b/drivers/staging/rtl8723bs/core/rtw_recv.c
> > @@ -1132,7 +1132,13 @@ static union recv_frame *recvframe_defrag(struct adapter *adapter,
> >  		/* append  to first fragment frame's tail (if privacy frame, pull the ICV) */
> >  		recvframe_pull_tail(prframe, pfhdr->attrib.icv_len);
> 
> There is no error checking on these pull calls.  They're supposed
> to return NULL if pfhdr->attrib.icv_len is too big.  (There is a similar
> caller earlier on the line before).
>

Actually if these fail

> >  
> > -		/* memcpy */
> > +		/* Verify the receiving buffer has enough space for the fragment */
> > +		if (pnfhdr->len > (uint)(pfhdr->rx_end - pfhdr->rx_tail)) {
> 

then the pfhdr->rx_end and pfhdr->rx_tail pointers are wrong.  So you
really do need to add the error checking before you do the resend.

regards,
dan carpenter



  reply	other threads:[~2026-04-15 16:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-05 10:15 [PATCH v3 0/5] staging: rtl8723bs: fix multiple missing bounds checks Delene Tchio Romuald
2026-04-05 10:15 ` [PATCH v3 1/5] staging: rtl8723bs: fix heap buffer overflow in recvframe_defrag() Delene Tchio Romuald
2026-04-15 13:56   ` Luka Gejak
2026-04-15 15:24   ` Dan Carpenter
2026-04-15 16:10     ` Dan Carpenter [this message]
2026-04-05 10:15 ` [PATCH v3 2/5] staging: rtl8723bs: fix integer underflow in TKIP MIC verification Delene Tchio Romuald
2026-04-15 13:56   ` Luka Gejak
2026-04-05 10:15 ` [PATCH v3 3/5] staging: rtl8723bs: fix out-of-bounds read in portctrl() Delene Tchio Romuald
2026-04-15 13:57   ` Luka Gejak
2026-04-05 10:15 ` [PATCH v3 4/5] staging: rtl8723bs: fix out-of-bounds reads in IE parsing functions Delene Tchio Romuald
2026-04-15 13:57   ` Luka Gejak
2026-04-05 10:15 ` [PATCH v3 5/5] staging: rtl8723bs: fix negative length in WEP decryption Delene Tchio Romuald
2026-04-15 13:57   ` Luka Gejak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ad-4h1qvjR_pki_v@stanley.mountain \
    --to=error27@gmail.com \
    --cc=delenetchior1@gmail.com \
    --cc=ethantidmore06@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=sam@samdaly.ie \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox