public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Zong-Zhe Yang <kevin_yang@realtek.com>,
	Dan Carpenter <dan.carpenter@linaro.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"kernel-janitors@vger.kernel.org"
	<kernel-janitors@vger.kernel.org>
Subject: RE: [PATCH v2 next] wifi: rtw89: mcc: prevent shift wrapping in rtw89_core_mlsr_switch()
Date: Thu, 29 May 2025 02:21:39 +0000	[thread overview]
Message-ID: <bb4bc20d9f7346edb013f123051fc490@realtek.com> (raw)
In-Reply-To: <a46c420109f0440a987d28c531dd39d6@realtek.com>

Zong-Zhe Yang <kevin_yang@realtek.com> wrote:
> Dan Carpenter <dan.carpenter@linaro.org> wrote:
> >
> > The "link_id" value comes from the user via debugfs.  If it's larger than BITS_PER_LONG then
> > that would result in shift wrapping and potentially an out of bounds access later.  In fact, we
> > can limit it to IEEE80211_MLD_MAX_NUM_LINKS (15).
> >
> > Fortunately, only root can write to debugfs files so the security impact is minimal.
> >
> > Fixes: 9dd85e739ce0 ("wifi: rtw89: debug: add mlo_mode dbgfs")
> > Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
> > ---
> > Use IEEE80211_MLD_MAX_NUM_LINKS as a limit instead of BITS_PER_LONG.
> > It's stricter and also more informative.
> >
> >  drivers/net/wireless/realtek/rtw89/core.c | 3 ++-
> >  1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/wireless/realtek/rtw89/core.c
> > b/drivers/net/wireless/realtek/rtw89/core.c
> > index 49447668cbf3..3604a8e15df0 100644
> > --- a/drivers/net/wireless/realtek/rtw89/core.c
> > +++ b/drivers/net/wireless/realtek/rtw89/core.c
> > @@ -5239,7 +5239,8 @@ int rtw89_core_mlsr_switch(struct rtw89_dev *rtwdev, struct
> > rtw89_vif *rtwvif,
> >         if (unlikely(!ieee80211_vif_is_mld(vif)))
> >                 return -EOPNOTSUPP;
> >
> > -       if (unlikely(!(usable_links & BIT(link_id)))) {
> > +       if (unlikely(link_id >= IEEE80211_MLD_MAX_NUM_LINKS ||
> > +                    !(usable_links & BIT(link_id)))) {
> >                 rtw89_warn(rtwdev, "%s: link id %u is not usable\n", __func__,
> >                            link_id);
> >                 return -ENOLINK;
> > --
> > 2.47.2
> 
> It looks good to me.
> Thank you.

I will add a tag during committing. 

Reviewed-by: Zong-Zhe Yang <kevin_yang@realtek.com>



  reply	other threads:[~2025-05-29  2:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-28  8:11 [PATCH v2 next] wifi: rtw89: mcc: prevent shift wrapping in rtw89_core_mlsr_switch() Dan Carpenter
2025-05-29  2:15 ` Zong-Zhe Yang
2025-05-29  2:21   ` Ping-Ke Shih [this message]
2025-06-10  1:31 ` Ping-Ke Shih

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=bb4bc20d9f7346edb013f123051fc490@realtek.com \
    --to=pkshih@realtek.com \
    --cc=dan.carpenter@linaro.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=kevin_yang@realtek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox