From: Linus Probert <linus.probert@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, error27@gmail.com
Cc: kernel-janitors@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org,
Linus Probert <linus.probert@gmail.com>
Subject: [PATCH] staging: rtl8723bs: fix potential speculative cpu oob read
Date: Wed, 29 Apr 2026 13:10:16 +0200 [thread overview]
Message-ID: <20260429111016.1260295-1-linus.probert@gmail.com> (raw)
Fixes potential speculative cpu oob read in os_intfs.c by guarding the
index with array_index_nospec.
Fixes smatch warning:
warn: potential spectre issue 'rtw_1d_to_queue' [r]
Signed-off-by: Linus Probert <linus.probert@gmail.com>
---
I can't argue with 100% certainty if this is a real risk. I found the
warning when I was testing out smatch (awesome work on that by the way)
and thought I'd take a look.
I did a quick search on the linux-staging list but couldn't find any
mention of 'spectre'. So as far as I could see it hasn't been brought up
before.
Was unsure if I should prefix this with RFC first.
drivers/staging/rtl8723bs/os_dep/os_intfs.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/rtl8723bs/os_dep/os_intfs.c b/drivers/staging/rtl8723bs/os_dep/os_intfs.c
index e943dcea1a21..8eea05111e79 100644
--- a/drivers/staging/rtl8723bs/os_dep/os_intfs.c
+++ b/drivers/staging/rtl8723bs/os_dep/os_intfs.c
@@ -347,7 +347,7 @@ static u16 rtw_select_queue(struct net_device *dev, struct sk_buff *skb,
if (pmlmepriv->acm_mask != 0)
skb->priority = qos_acm(pmlmepriv->acm_mask, skb->priority);
- return rtw_1d_to_queue[skb->priority];
+ return rtw_1d_to_queue[array_index_nospec(skb->priority, ARRAY_SIZE(rtw_1d_to_queue))];
}
u16 rtw_recv_select_queue(struct sk_buff *skb)
@@ -374,7 +374,7 @@ u16 rtw_recv_select_queue(struct sk_buff *skb)
priority = 0;
}
- return rtw_1d_to_queue[priority];
+ return rtw_1d_to_queue[array_index_nospec(priority, ARRAY_SIZE(rtw_1d_to_queue))];
}
static int rtw_ndev_init(struct net_device *dev)
--
2.54.0
next reply other threads:[~2026-04-29 11:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 11:10 Linus Probert [this message]
2026-04-29 11:31 ` [PATCH] staging: rtl8723bs: fix potential speculative cpu oob read Greg Kroah-Hartman
2026-04-29 12:45 ` Linus Probert
2026-04-29 13:53 ` Greg Kroah-Hartman
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=20260429111016.1260295-1-linus.probert@gmail.com \
--to=linus.probert@gmail.com \
--cc=error27@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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