From: "Luka Gejak" <luka.gejak@linux.dev>
To: "Delene Tchio Romuald" <delenetchior1@gmail.com>,
<gregkh@linuxfoundation.org>
Cc: "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 15:56:44 +0200 [thread overview]
Message-ID: <DHTS483VGY68.2WFIJPWPCVXB5@linux.dev> (raw)
In-Reply-To: <20260405101548.124829-2-delenetchior1@gmail.com>
On Sun Apr 5, 2026 at 12:15 PM CEST, Delene Tchio Romuald wrote:
> In recvframe_defrag(), a memcpy() copies fragment data into the
> reassembly buffer before recvframe_put() validates that the buffer
> has sufficient space. If the total reassembled payload exceeds the
> receive buffer capacity, this results in a heap buffer overflow.
>
> An attacker within WiFi radio range can exploit this by sending
> crafted 802.11 fragmented frames. No authentication is required.
>
> Add a bounds check before the memcpy() to verify that the fragment
> payload fits within the remaining buffer space, using the same error
> handling pattern already present in the function.
>
> Found by reviewing memory operations in the driver and tracing
> buffer pointer manipulation through rtw_recv.h inline helpers.
> Not tested on hardware.
>
> Signed-off-by: Delene Tchio Romuald <delenetchior1@gmail.com>
> ---
> v3:
> - Rebased on staging-next
> - Sent as numbered series with proper Cc from get_maintainer.pl
> v2:
> - Rebased on staging-next (v1 was based on v7.0-rc6 and did not apply)
> - Removed Cc: stable (will be added by maintainer)
>
> drivers/staging/rtl8723bs/core/rtw_recv.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> 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);
>
> - /* memcpy */
> + /* Verify the receiving buffer has enough space for the fragment */
> + if (pnfhdr->len > (uint)(pfhdr->rx_end - pfhdr->rx_tail)) {
> + rtw_free_recvframe(prframe, pfree_recv_queue);
> + rtw_free_recvframe_queue(defrag_q, pfree_recv_queue);
> + return NULL;
> + }
> +
> memcpy(pfhdr->rx_tail, pnfhdr->rx_data, pnfhdr->len);
>
> recvframe_put(prframe, pnfhdr->len);
LGTM.
Reviewed-by: Luka Gejak <luka.gejak@linux.dev>
Best regards,
Luka Gejak
next prev parent reply other threads:[~2026-04-15 13:57 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 [this message]
2026-04-15 15:24 ` Dan Carpenter
2026-04-15 16:10 ` Dan Carpenter
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=DHTS483VGY68.2WFIJPWPCVXB5@linux.dev \
--to=luka.gejak@linux.dev \
--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