mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Adi Prasan <itsadi2409@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	error27@gmail.com
Subject: Re: [PATCH v3] staging: rtl8723bs: fix ie_length bound check in rtw_cfg80211_inform_bss
Date: Fri, 2 Oct 2026 16:52:59 +0200	[thread overview]
Message-ID: <2026100246-underpaid-hardener-cfab@gregkh> (raw)
In-Reply-To: <20261002140450.3209-1-itsadi2409@gmail.com>

On Fri, Oct 02, 2026 at 02:04:50PM +0000, Adi Prasan wrote:
> The buffer bound check in rtw_cfg80211_inform_bss() checked bssinf_len
> (ie_length + header size) against MAX_BSSINFO_LEN (1000 bytes), but
> network.ies[] is only MAX_IE_SZ (768) bytes. This allowed ie_length
> values up to ~976 bytes to pass the check while a subsequent memcpy()
> from network.ies still only has 768 valid bytes, and other paths that
> write to network.ies consistently cap ie_length to MAX_IE_SZ.
> 
> Check ie_length against MAX_IE_SZ directly, which is the actual size
> of network.ies, and drop the now-unused bssinf_len/MAX_BSSINFO_LEN
> comparison.
> 
> Signed-off-by: Adi Prasan <itsadi2409@gmail.com>
> Fixes: 554c0a3abf216 ("staging: Add rtl8723bs sdio wifi driver")
> ---
>  drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c b/drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c
> index 27e7b8442d7b..7e964b15ae6d 100644
> --- a/drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c
> +++ b/drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c
> @@ -210,7 +210,7 @@ struct cfg80211_bss *rtw_cfg80211_inform_bss(struct adapter *padapter, struct wl
>  	u64 notify_timestamp;
>  	s32 notify_signal;
>  	u8 *buf = NULL, *pbuf;
> -	size_t len, bssinf_len = 0;
> +	size_t len;
>  	struct ieee80211_hdr *pwlanhdr;
>  	__le16 *fctrl;
>  
> @@ -218,8 +218,7 @@ struct cfg80211_bss *rtw_cfg80211_inform_bss(struct adapter *padapter, struct wl
>  	struct wiphy *wiphy = wdev->wiphy;
>  	struct mlme_priv *pmlmepriv = &(padapter->mlmepriv);
>  
> -	bssinf_len = pnetwork->network.ie_length + sizeof(struct ieee80211_hdr_3addr);
> -	if (bssinf_len > MAX_BSSINFO_LEN || pnetwork->network.ie_length > MAX_IE_SZ)
> +	if (pnetwork->network.ie_length > MAX_IE_SZ)
>  		goto exit;
>  
>  	{
> -- 
> 2.43.0
> 

Hi,

This is the friendly patch-bot of Greg Kroah-Hartman.  You have sent him
a patch that has triggered this response.  He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created.  Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.

You are receiving this message because of the following common error(s)
as indicated below:

- This looks like a new version of a previously submitted patch, but you
  did not list below the --- line any changes from the previous version.
  Please read the section entitled "The canonical patch format" in the
  kernel file, Documentation/process/submitting-patches.rst for what
  needs to be done here to properly describe this.

- You have marked a patch with a "Fixes:" tag for a commit that is in an
  older released kernel, yet you do not have a cc: stable line in the
  signed-off-by area at all, which means that the patch will not be
  applied to any older kernel releases.  To properly fix this, please
  follow the documented rules in the
  Documentation/process/stable-kernel-rules.rst file for how to resolve
  this.

If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.

thanks,

greg k-h's patch email bot

      reply	other threads:[~2026-10-02 14:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-20 14:28 [PATCH] " Adi Prasan
2026-09-20 15:37 ` Greg KH
2026-09-21  5:13   ` Adi Prasan
2026-09-21 15:23 ` Dan Carpenter
2026-09-21 17:03   ` Adi Prasan
2026-09-22  7:48     ` Dan Carpenter
2026-09-21 16:55 ` [PATCH v2] " Adi Prasan
2026-09-22 10:22   ` Dan Carpenter
     [not found]     ` <CAAd6oEjAMrJjx6PLDE7jj5OsgbwFWU9Uoy=_UyO8w-5AyZCxqw@mail.gmail.com>
2026-10-02  7:25       ` Dan Carpenter
2026-10-02 14:06         ` [PATCH] " Adi Prasan
2026-10-02 14:04 ` [PATCH v3] " Adi Prasan
2026-10-02 14:52   ` Greg KH [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=2026100246-underpaid-hardener-cfab@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=error27@gmail.com \
    --cc=itsadi2409@gmail.com \
    --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

all inboxes | Powered by JetHome®