Linux wireless drivers development
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: LB F <goainwo@gmail.com>,
	Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
	Fiona Klute <fiona.klute@gmx.de>,
	"andrej.skvortzov@gmail.com" <andrej.skvortzov@gmail.com>,
	"anarsoul@gmail.com" <anarsoul@gmail.com>,
	Zhen XIN <zhen.xin@nokia-sbell.com>
Subject: RE: [PATCH rtw-next] wifi: rtw88: Add more validation for the RX descriptor
Date: Mon, 18 May 2026 08:14:59 +0000	[thread overview]
Message-ID: <1d0efa51a4214ee8b65d7f3ff9d52097@realtek.com> (raw)
In-Reply-To: <a237ba9e-9f05-451f-9dfc-9aa8b11b7bc4@gmail.com>

Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
> Some RTL8821CE cards can return frames with corrupted RX descriptor,
> causing warnings and crashes if they are passed to the upper layers.

Not sure if this is the reason Larry uploaded a copy of vendor driver
to his repository [1]. 

Recently, we received vulnerability report of rtw_mp_efuse_set() in
vendor driver. I'd like to know if people are still using the vendor
driver [1]. If not, is it possible to remove it? If people still need it,
I will share the fix made by our internal later.

[1] https://github.com/lwfinger/rtw88/tree/master/alt_rtl8821ce

> 
> The PHY status size field is 4 bits wide, but in rtw88 its value should
> only be 0 or 4. Checking this catches most of the corrupt frames.
> 
> If a PHY status is present, the PHY status size should not be 0.
> 
> The frame size should not be less than or equal to 4 and should not
> exceed 11454.
> 
> Discard the frame if any of these checks fail.
> 
> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=221286
> Signed-off-by: Bitterblue Smith <rtl8821cerfe2@gmail.com>

Acked-by: Ping-Ke Shih <pkshih@realtek.com>

[...]

> diff --git a/drivers/net/wireless/realtek/rtw88/rx.c b/drivers/net/wireless/realtek/rtw88/rx.c
> index d9e11343d498..65f6db3d7fcb 100644
> --- a/drivers/net/wireless/realtek/rtw88/rx.c
> +++ b/drivers/net/wireless/realtek/rtw88/rx.c
> @@ -3,6 +3,7 @@
>   */
> 
>  #include "main.h"
> +#include "mac.h"
>  #include "rx.h"
>  #include "ps.h"
>  #include "debug.h"
> @@ -261,9 +262,9 @@ static void rtw_rx_fill_rx_status(struct rtw_dev *rtwdev,
>         }
>  }
> 
> -void rtw_rx_query_rx_desc(struct rtw_dev *rtwdev, void *rx_desc8,
> -                         struct rtw_rx_pkt_stat *pkt_stat,
> -                         struct ieee80211_rx_status *rx_status)
> +int rtw_rx_query_rx_desc(struct rtw_dev *rtwdev, void *rx_desc8,
> +                        struct rtw_rx_pkt_stat *pkt_stat,
> +                        struct ieee80211_rx_status *rx_status)
>  {
>         u32 desc_sz = rtwdev->chip->rx_pkt_desc_sz;
>         struct rtw_rx_desc *rx_desc = rx_desc8;
> @@ -303,12 +304,25 @@ void rtw_rx_query_rx_desc(struct rtw_dev *rtwdev, void *rx_desc8,
>                 pkt_stat->bw = RTW_CHANNEL_WIDTH_20;

Do you think if we should return -EINVAL for this case too?

>         }
> 
> +       if (unlikely(pkt_stat->drv_info_sz &&
> +                    pkt_stat->drv_info_sz != PHY_STATUS_SIZE))
> +               return -EINVAL;
> +
> +       if (unlikely(pkt_stat->phy_status && !pkt_stat->drv_info_sz))
> +               return -EINVAL;
> +
> +       if (unlikely(pkt_stat->pkt_len > IEEE80211_MAX_MPDU_LEN_VHT_11454))
> +               return -EINVAL;
> +
>         /* drv_info_sz is in unit of 8-bytes */
>         pkt_stat->drv_info_sz *= 8;
> 
>         /* c2h cmd pkt's rx/phy status is not interested */
>         if (pkt_stat->is_c2h)
> -               return;
> +               return 0;
> +
> +       if (unlikely(pkt_stat->pkt_len <= FCS_LEN))
> +               return -EINVAL;
> 
>         phy_status = rx_desc8 + desc_sz + pkt_stat->shift;
>         hdr = phy_status + pkt_stat->drv_info_sz;

[...]


  parent reply	other threads:[~2026-05-18  8:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-16 14:44 [PATCH rtw-next] wifi: rtw88: Add more validation for the RX descriptor Bitterblue Smith
2026-05-17 16:17 ` Oleksandr Havrylov
2026-05-18  8:14 ` Ping-Ke Shih [this message]
2026-05-19 17:59   ` Bitterblue Smith
2026-05-20  1:45     ` 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=1d0efa51a4214ee8b65d7f3ff9d52097@realtek.com \
    --to=pkshih@realtek.com \
    --cc=anarsoul@gmail.com \
    --cc=andrej.skvortzov@gmail.com \
    --cc=fiona.klute@gmx.de \
    --cc=goainwo@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=rtl8821cerfe2@gmail.com \
    --cc=zhen.xin@nokia-sbell.com \
    /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