From: Luka Gejak <luka.gejak@linux.dev>
To: Alexandru Hossu <hossu.alexandru@gmail.com>, gregkh@linuxfoundation.org
Cc: dan.carpenter@linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, hossu.alexandru@gmail.com,
luka.gejak@linux.dev
Subject: Re: [PATCH v2 0/3] staging: rtl8723bs: fix OOB reads and heap overflow in IE parsing
Date: Sun, 26 Apr 2026 12:29:47 +0200 [thread overview]
Message-ID: <DC7CC9BA-409F-499C-BAD3-8ED124CCDED1@linux.dev> (raw)
In-Reply-To: <20260426095156.3523480-1-hossu.alexandru@gmail.com>
On April 26, 2026 11:51:53 AM GMT+02:00, Alexandru Hossu <hossu.alexandru@gmail.com> wrote:
...
>This series fixes three related bugs in the rtl8723bs staging driver's
>802.11 IE parsing code. All three share the same root cause: IE parsing
>loops and IE handler functions do not check that an IE's declared length
>actually fits within the remaining buffer before reading from it.
...
If these are bug fixes(which they appear to be) they should have Fixes
tag present as well as cc for stable if they are present in stabe tree
too. Also Reviewed-by tag goes above your Signed-off-by tag. Please
send v3 with these changes.
Best regards,
Luka Gejak
prev parent reply other threads:[~2026-04-26 10:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-26 9:51 [PATCH v2 0/3] staging: rtl8723bs: fix OOB reads and heap overflow in IE parsing Alexandru Hossu
2026-04-26 9:51 ` [PATCH v2 1/3] staging: rtl8723bs: fix OOB read in update_beacon_info() IE loop Alexandru Hossu
2026-04-26 9:51 ` [PATCH v2 2/3] staging: rtl8723bs: fix OOB reads in IE loops in issue_assocreq() and join_cmd_hdl() Alexandru Hossu
2026-04-26 9:51 ` [PATCH v2 3/3] staging: rtl8723bs: fix heap buffer overflow in rtw_cfg80211_set_wpa_ie() Alexandru Hossu
2026-04-26 10:29 ` Luka Gejak [this message]
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=DC7CC9BA-409F-499C-BAD3-8ED124CCDED1@linux.dev \
--to=luka.gejak@linux.dev \
--cc=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=hossu.alexandru@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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