From: Dan Carpenter <error27@gmail.com>
To: Delene Tchio Romuald <delenetchior1@gmail.com>
Cc: gregkh@linuxfoundation.org, luka.gejak@linux.dev,
hansg@kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v5 3/5] staging: rtl8723bs: fix out-of-bounds read in portctrl()
Date: Fri, 17 Apr 2026 08:35:46 +0300 [thread overview]
Message-ID: <aeHGsjwV5_qIuT5U@stanley.mountain> (raw)
In-Reply-To: <20260417030110.42991-4-delenetchior1@gmail.com>
On Fri, Apr 17, 2026 at 04:01:08AM +0100, Delene Tchio Romuald wrote:
> drivers/staging/rtl8723bs/core/rtw_recv.c | 21 +++++++++++++--------
> 1 file changed, 13 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/staging/rtl8723bs/core/rtw_recv.c b/drivers/staging/rtl8723bs/core/rtw_recv.c
> index 40884788a30d6..b11982fbe7e1f 100644
> --- a/drivers/staging/rtl8723bs/core/rtw_recv.c
> +++ b/drivers/staging/rtl8723bs/core/rtw_recv.c
> @@ -537,20 +537,25 @@ static union recv_frame *portctrl(struct adapter *adapter, union recv_frame *pre
> /* blocked */
> /* only accept EAPOL frame */
>
> - prtnframe = precv_frame;
> + /* Ensure frame has LLC header and ether_type */
> + if (pfhdr->len < pattrib->hdrlen +
> + pattrib->iv_len + LLC_HEADER_LENGTH + 2) {
> + rtw_free_recvframe(precv_frame,
> + &adapter->recvpriv.free_recv_queue);
> + return NULL;
> + }
>
> /* get ether_type */
> - ptr = ptr + pfhdr->attrib.hdrlen + pfhdr->attrib.iv_len + LLC_HEADER_LENGTH;
> + ptr += pattrib->hdrlen + pattrib->iv_len + LLC_HEADER_LENGTH;
Don't do this unrelated cleanup.
> memcpy(&be_tmp, ptr, 2);
> ether_type = ntohs(be_tmp);
>
> - if (ether_type == eapol_type)
> - prtnframe = precv_frame;
> - else {
> - /* free this frame */
> - rtw_free_recvframe(precv_frame, &adapter->recvpriv.free_recv_queue);
> - prtnframe = NULL;
> + if (ether_type != eapol_type) {
> + rtw_free_recvframe(precv_frame,
> + &adapter->recvpriv.free_recv_queue);
> + return NULL;
> }
> + prtnframe = precv_frame;
Same. If you really want to do it, it has to be in a separate patch.
regards,
dan carpenter
> } else {
> /* allowed */
> /* check decryption status, and decrypt the frame if needed */
next prev parent reply other threads:[~2026-04-17 5:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 3:01 [PATCH v5 0/5] staging: rtl8723bs: fix multiple security vulnerabilities Delene Tchio Romuald
2026-04-17 3:01 ` [PATCH v5 1/5] staging: rtl8723bs: fix heap buffer overflow in recvframe_defrag() Delene Tchio Romuald
2026-04-17 5:31 ` Dan Carpenter
2026-04-17 3:01 ` [PATCH v5 2/5] staging: rtl8723bs: fix integer underflow in TKIP MIC verification Delene Tchio Romuald
2026-04-17 3:01 ` [PATCH v5 3/5] staging: rtl8723bs: fix out-of-bounds read in portctrl() Delene Tchio Romuald
2026-04-17 5:35 ` Dan Carpenter [this message]
2026-04-17 3:01 ` [PATCH v5 4/5] staging: rtl8723bs: fix out-of-bounds reads in IE parsing functions Delene Tchio Romuald
2026-04-17 3:01 ` [PATCH v5 5/5] staging: rtl8723bs: fix negative length in WEP decryption Delene Tchio Romuald
2026-04-17 5:35 ` [PATCH v5 0/5] staging: rtl8723bs: fix multiple security vulnerabilities Dan Carpenter
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=aeHGsjwV5_qIuT5U@stanley.mountain \
--to=error27@gmail.com \
--cc=delenetchior1@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=luka.gejak@linux.dev \
--cc=stable@vger.kernel.org \
/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