From: Ping-Ke Shih <pkshih@realtek.com>
To: Ali Tariq <alitariq45892@gmail.com>, <Jes.Sorensen@gmail.com>
Cc: <linux-wireless@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>,
Ali Tariq <alitariq45892@gmail.com>
Subject: Re: [PATCH] rtl8xxxu: fix slab-out-of-bounds in rtl8xxxu_sta_add
Date: Wed, 31 Dec 2025 16:08:11 +0800 [thread overview]
Message-ID: <f05788ea-fb2d-4152-a4cd-016d4f5e8273@RTKEXHMBS03.realtek.com.tw> (raw)
In-Reply-To: <20251225115430.13011-1-alitariq45892@gmail.com>
Ali Tariq <alitariq45892@gmail.com> wrote:
> The driver does not set hw->sta_data_size, which causes mac80211 to
> allocate insufficient space for driver private station data in
> __sta_info_alloc(). When rtl8xxxu_sta_add() accesses members of
> struct rtl8xxxu_sta_info through sta->drv_priv, this results in a
> slab-out-of-bounds write.
>
> KASAN report on RISC-V (VisionFive 2) with RTL8192EU adapter:
>
> BUG: KASAN: slab-out-of-bounds in rtl8xxxu_sta_add+0x31c/0x346
> Write of size 8 at addr ffffffd6d3e9ae88 by task kworker/u16:0/12
>
> Set hw->sta_data_size to sizeof(struct rtl8xxxu_sta_info) during
> probe, similar to how hw->vif_data_size is configured. This ensures
> mac80211 allocates sufficient space for the driver's per-station
> private data.
>
> Tested on StarFive VisionFive 2 v1.2A board.
>
> Fixes: eef55f1545c9 ("wifi: rtl8xxxu: support multiple interfaces in {add,remove}_interface()")
>
> Cc: stable@vger.kernel.org
>
> Signed-off-by: Ali Tariq <alitariq45892@gmail.com>
> Reviewed-by: Ping-Ke Shih <pkshih@realtek.com>
1 patch(es) applied to rtw-next branch of rtw.git, thanks.
86c946bcc00f wifi: rtl8xxxu: fix slab-out-of-bounds in rtl8xxxu_sta_add
---
https://github.com/pkshih/rtw.git
prev parent reply other threads:[~2025-12-31 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-25 11:54 Ali Tariq
2025-12-26 1:55 ` Ping-Ke Shih
2025-12-31 8:08 ` Ping-Ke Shih [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=f05788ea-fb2d-4152-a4cd-016d4f5e8273@RTKEXHMBS03.realtek.com.tw \
--to=pkshih@realtek.com \
--cc=Jes.Sorensen@gmail.com \
--cc=alitariq45892@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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
all inboxes | Powered by JetHome®