All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: alex bestoso <alexbestoso@bestosotech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: Bug Report - Rtlwifi
Date: Thu, 27 Nov 2025 06:37:09 +0000	[thread overview]
Message-ID: <0b376fdcc68442f7b41268bb26cce73e@realtek.com> (raw)
In-Reply-To: <85517aee-6e2a-4524-a5e2-6b48d05facbe@bestosotech.com>

alex bestoso <alexbestoso@bestosotech.com> wrote:
> Bug Description : 
>     Index out of range. Problem happens on it's own after being connected to a network for a short while.
> 
> Error message : 
>     UBSAN: array-index-out-of-bounds in drivers/net/wireless/realtek/rtlwifi/rtl8192cu/trx.c:514:30
>     [  454.351041] index 10 is out of range for type 'rtl_tid_data [9]'
> 
> Kernel Version : 
>     6.18.0-rc6+
> 
> Suggested Solution: 
>     change the file drivers/net/wireless/realtek/rtlwifi/rtl8192cu/trx.c from 
> 
>     513     tid = ieee80211_get_tid(hdr);
>     514     agg_state = sta_entry->tids[tid].agg.agg_state;
>     515     ampdu_density = sta->deflink.ht_cap.ampdu_density;
> 
>     to
> 
>     513     tid = ieee80211_get_tid(hdr);
>     514     if(tid < MAX_TID_COUNT)
>     515         agg_state = sta_entry->tids[tid].agg.agg_state;
>     516     ampdu_density = sta->deflink.ht_cap.ampdu_density;

This change is fine to me. Can you send a patch?


       reply	other threads:[~2025-11-27  6:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <85517aee-6e2a-4524-a5e2-6b48d05facbe@bestosotech.com>
2025-11-27  6:37 ` Ping-Ke Shih [this message]
2025-11-27  6:55   ` Bug Report - Rtlwifi alex bestoso
2025-11-27  7:50     ` Ping-Ke Shih
2025-11-27 15:09       ` alex bestoso

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=0b376fdcc68442f7b41268bb26cce73e@realtek.com \
    --to=pkshih@realtek.com \
    --cc=alexbestoso@bestosotech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.