From: Alexandru Hossu <hossu.alexandru@gmail.com>
To: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Cc: error27@gmail.com, stable@vger.kernel.org, luka.gejak@linux.dev,
hansg@kernel.org, Alexandru Hossu <hossu.alexandru@gmail.com>
Subject: [PATCH v7 1/2] staging: rtl8723bs: fix Challenge Text IE length checks in OnAuthClient() and OnAuth()
Date: Tue, 5 May 2026 23:13:15 +0200 [thread overview]
Message-ID: <20260505211316.3837020-2-hossu.alexandru@gmail.com> (raw)
In-Reply-To: <20260505211316.3837020-1-hossu.alexandru@gmail.com>
Two functions process Challenge Text IEs without verifying that the IE
length matches the 128-byte buffer:
1. OnAuthClient() shared key path (STA mode).
rtw_get_ie() returns the raw IE length from the received frame,
which can be up to 255. This length is used directly in memcpy()
into chg_txt[128] with no bounds check, allowing a heap overflow of
up to 127 bytes when a rogue AP sends an Auth seq=2 frame with a
Challenge Text IE longer than 128 bytes.
2. OnAuth() sequence 3 path (AP mode).
When a STA completes shared-key authentication, OnAuth() calls
rtw_get_ie() to find the Challenge Text IE, checks only that the
IE is present and has nonzero length, then calls
memcmp((p + 2), pstat->chg_txt, 128). If a rogue STA sends a
Challenge Text IE shorter than 128 bytes, memcmp reads past the
end of the IE payload into adjacent packet data, causing an
out-of-bounds read.
IEEE 802.11 mandates the Challenge Text element carries exactly 128
bytes of challenge data. Add len != sizeof(pmlmeinfo->chg_txt) and
ie_len != sizeof(pstat->chg_txt) guards to reject any element whose
length field does not match.
Fixes: 554c0a3abf21 ("staging: Add rtl8723bs sdio wifi driver")
Cc: stable@vger.kernel.org
Signed-off-by: Alexandru Hossu <hossu.alexandru@gmail.com>
---
Changes in v7:
- No code changes from v6; dropping Reviewed-by: Dan Carpenter because
patch 2/2 changes code from the reviewed version.
drivers/staging/rtl8723bs/core/rtw_mlme_ext.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/rtl8723bs/core/rtw_mlme_ext.c b/drivers/staging/rtl8723bs/core/rtw_mlme_ext.c
index 5f00fe282d1b..dd3c94d314d8 100644
--- a/drivers/staging/rtl8723bs/core/rtw_mlme_ext.c
+++ b/drivers/staging/rtl8723bs/core/rtw_mlme_ext.c
@@ -802,7 +802,7 @@ unsigned int OnAuth(struct adapter *padapter, union recv_frame *precv_frame)
p = rtw_get_ie(pframe + WLAN_HDR_A3_LEN + 4 + _AUTH_IE_OFFSET_, WLAN_EID_CHALLENGE, (int *)&ie_len,
len - WLAN_HDR_A3_LEN - _AUTH_IE_OFFSET_ - 4);
- if (!p || ie_len <= 0) {
+ if (!p || ie_len != sizeof(pstat->chg_txt)) {
status = WLAN_STATUS_CHALLENGE_FAIL;
goto auth_fail;
}
@@ -891,7 +891,7 @@ unsigned int OnAuthClient(struct adapter *padapter, union recv_frame *precv_fram
p = rtw_get_ie(pframe + WLAN_HDR_A3_LEN + _AUTH_IE_OFFSET_, WLAN_EID_CHALLENGE, (int *)&len,
pkt_len - WLAN_HDR_A3_LEN - _AUTH_IE_OFFSET_);
- if (!p)
+ if (!p || len != sizeof(pmlmeinfo->chg_txt))
goto authclnt_fail;
memcpy(pmlmeinfo->chg_txt, p + 2, len);
--
2.53.0
next prev parent reply other threads:[~2026-05-05 21:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 9:45 [PATCH v6 1/2] staging: rtl8723bs: fix heap overflow in OnAuthClient shared key path Alexandru Hossu
2026-04-15 9:45 ` [PATCH v6 2/2] staging: rtl8723bs: fix missing frame length checks in OnAuthClient Alexandru Hossu
2026-04-15 11:09 ` [PATCH v6 1/2] staging: rtl8723bs: fix heap overflow in OnAuthClient shared key path Luka Gejak
2026-05-04 14:10 ` Greg KH
2026-05-05 21:13 ` [PATCH v7 0/2] staging: rtl8723bs: fix OOB reads in OnAuth() and OnAuthClient() Alexandru Hossu
2026-05-05 21:13 ` Alexandru Hossu [this message]
2026-05-05 21:13 ` [PATCH v7 2/2] staging: rtl8723bs: fix missing frame length checks " Alexandru Hossu
2026-05-11 12:43 ` [PATCH v7 0/2] staging: rtl8723bs: fix OOB reads " Greg KH
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=20260505211316.3837020-2-hossu.alexandru@gmail.com \
--to=hossu.alexandru@gmail.com \
--cc=error27@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