From: Greg KH <gregkh@linuxfoundation.org>
To: Alexandru Hossu <hossu.alexandru@gmail.com>
Cc: linux-staging@lists.linux.dev, stable@vger.kernel.org
Subject: Re: [PATCH v6 0/7] staging: rtl8723bs: fix OOB reads and writes in IE/attribute parsing
Date: Thu, 21 May 2026 16:11:09 +0200 [thread overview]
Message-ID: <2026052158-mumps-margarita-afcd@gregkh> (raw)
In-Reply-To: <20260521130330.754181-1-hossu.alexandru@gmail.com>
On Thu, May 21, 2026 at 03:03:23PM +0200, Alexandru Hossu wrote:
> Fix out-of-bounds memory accesses in several IE and attribute parsing
> paths of the rtl8723bs driver. All affected functions iterate over
> attacker-controlled IE data from over-the-air frames without validating
> header or payload bounds before dereferencing.
>
> v6: add two patches addressing issues found during v5 review.
> Patch 6 adds IE header bounds checks and payload length guards to
> is_ap_in_tkip(). Patch 7 adds header and payload bounds checks to
> rtw_get_sec_ie(), rtw_get_wapi_ie(), and rtw_get_wps_attr().
>
You have to show all the version info for all versions :(
next prev parent reply other threads:[~2026-05-21 14:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 13:03 [PATCH v6 0/7] staging: rtl8723bs: fix OOB reads and writes in IE/attribute parsing Alexandru Hossu
2026-05-21 13:03 ` [PATCH v6 1/7] staging: rtl8723bs: fix OOB read in update_beacon_info() IE loop Alexandru Hossu
2026-05-21 13:03 ` [PATCH v6 2/7] staging: rtl8723bs: fix OOB reads in IE loops in issue_assocreq() and join_cmd_hdl() Alexandru Hossu
2026-05-21 13:03 ` [PATCH v6 3/7] staging: rtl8723bs: fix heap buffer overflow in rtw_cfg80211_set_wpa_ie() Alexandru Hossu
2026-05-21 13:03 ` [PATCH v6 4/7] staging: rtl8723bs: fix OOB write in HT_caps_handler() Alexandru Hossu
2026-05-21 13:03 ` [PATCH v6 5/7] staging: rtl8723bs: fix OOB read in OnAssocRsp() IE loop Alexandru Hossu
2026-05-21 13:03 ` [PATCH v6 6/7] staging: rtl8723bs: fix OOB reads in is_ap_in_tkip() " Alexandru Hossu
2026-05-21 13:03 ` [PATCH v6 7/7] staging: rtl8723bs: fix OOB reads in rtw_get_sec_ie(), rtw_get_wapi_ie(), and rtw_get_wps_attr() Alexandru Hossu
2026-05-21 14:11 ` Greg KH [this message]
2026-05-21 14:18 ` [PATCH v6 0/7] staging: rtl8723bs: fix OOB reads and writes in IE/attribute parsing Alexandru Hossu
2026-05-22 0:45 ` [PATCH v7 " Alexandru Hossu
2026-05-22 0:45 ` [PATCH v7 1/7] staging: rtl8723bs: fix OOB read in update_beacon_info() IE loop Alexandru Hossu
2026-05-22 0:45 ` [PATCH v7 2/7] staging: rtl8723bs: fix OOB reads in IE loops in issue_assocreq() and join_cmd_hdl() Alexandru Hossu
2026-05-22 0:45 ` [PATCH v7 3/7] staging: rtl8723bs: fix heap buffer overflow in rtw_cfg80211_set_wpa_ie() Alexandru Hossu
2026-05-22 0:45 ` [PATCH v7 4/7] staging: rtl8723bs: fix OOB write in HT_caps_handler() Alexandru Hossu
2026-05-22 0:45 ` [PATCH v7 5/7] staging: rtl8723bs: fix OOB read in OnAssocRsp() IE loop Alexandru Hossu
2026-05-22 0:45 ` [PATCH v7 6/7] staging: rtl8723bs: fix OOB reads in is_ap_in_tkip() " Alexandru Hossu
2026-05-22 0:45 ` [PATCH v7 7/7] staging: rtl8723bs: fix OOB reads in rtw_get_sec_ie(), rtw_get_wapi_ie(), and rtw_get_wps_attr() Alexandru Hossu
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=2026052158-mumps-margarita-afcd@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=hossu.alexandru@gmail.com \
--cc=linux-staging@lists.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