The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Laxman Acharya Padhya <acharyalaxman8848@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: RE: [PATCH] wifi: rtw89: cap firmware section_num before parsing
Date: Tue, 25 Aug 2026 03:54:14 +0000	[thread overview]
Message-ID: <26bf80f23bfa4fe49183d1f724fffc5c@realtek.com> (raw)
In-Reply-To: <20260822080014.29611-1-acharyalaxman8848@gmail.com>

Laxman Acharya Padhya <acharyalaxman8848@gmail.com> wrote:
> rtw89_fw_bin_info.section_info has FWDL_SECTION_MAX_NUM (10) entries.
> The v0/v1 header parsers take section_num from an 8-bit firmware field
> (0..255) and write info->section_info[i] with no cap.
> rtw89_fw_download_suit() keeps that object on the stack, so a crafted
> firmware blob overflows the stack.
> 
> Reject a truncated header and a section table that does not fit in the
> firmware image before reading fw_hdr->sections[i].
> 
> Cc: stable@vger.kernel.org
> Signed-off-by: Laxman Acharya Padhya <acharyalaxman8848@gmail.com>

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

Logic is good to me, but please add empty lines. 

> ---
>  drivers/net/wireless/realtek/rtw89/fw.c | 30 +++++++++++++++++++++++++
>  1 file changed, 30 insertions(+)
> 
> diff --git a/drivers/net/wireless/realtek/rtw89/fw.c b/drivers/net/wireless/realtek/rtw89/fw.c
> index 0099c5c03e7a6..57d4252ee78f0 100644
> --- a/drivers/net/wireless/realtek/rtw89/fw.c
> +++ b/drivers/net/wireless/realtek/rtw89/fw.c
> @@ -156,8 +156,23 @@ static int rtw89_fw_hdr_parser_v0(struct rtw89_dev *rtwdev, const u8 *fw, u32 le
>         if (!info)
>                 return -EINVAL;
> 
> +       if (len < sizeof(*fw_hdr)) {
> +               rtw89_err(rtwdev, "[ERR]fw header truncated\n");
> +               return -EINVAL;
> +       }
> +
>         info->section_num = le32_get_bits(fw_hdr->w6, FW_HDR_W6_SEC_NUM);
> +       if (!info->section_num || info->section_num > FWDL_SECTION_MAX_NUM) {
> +               rtw89_err(rtwdev, "[ERR]invalid fw section num %u\n",
> +                         info->section_num);
> +               return -EINVAL;
> +       }
> +
>         base_hdr_len = struct_size(fw_hdr, sections, info->section_num);
> +       if (base_hdr_len > len) {
> +               rtw89_err(rtwdev, "[ERR]fw header truncated\n");
> +               return -EINVAL;
> +       }

an empty line

>         info->dynamic_hdr_en = le32_get_bits(fw_hdr->w7, FW_HDR_W7_DYN_HDR);
>         info->idmem_share_mode = le32_get_bits(fw_hdr->w7, FW_HDR_W7_IDMEM_SHARE_MODE);
> 
> @@ -455,9 +470,24 @@ static int rtw89_fw_hdr_parser_v1(struct rtw89_dev *rtwdev, const u8 *fw, u32 le
>         int ret;
>         u32 i;
> 
> +       if (len < sizeof(*fw_hdr)) {
> +               rtw89_err(rtwdev, "[ERR]fw header truncated\n");
> +               return -EINVAL;
> +       }
> +
>         info->section_num = le32_get_bits(fw_hdr->w6, FW_HDR_V1_W6_SEC_NUM);
> +       if (!info->section_num || info->section_num > FWDL_SECTION_MAX_NUM) {
> +               rtw89_err(rtwdev, "[ERR]invalid fw section num %u\n",
> +                         info->section_num);
> +               return -EINVAL;
> +       }
> +
>         info->dsp_checksum = le32_get_bits(fw_hdr->w6, FW_HDR_V1_W6_DSP_CHKSUM);
>         base_hdr_len = struct_size(fw_hdr, sections, info->section_num);
> +       if (base_hdr_len > len) {
> +               rtw89_err(rtwdev, "[ERR]fw header truncated\n");
> +               return -EINVAL;
> +       }

an empty line

>         info->dynamic_hdr_en = le32_get_bits(fw_hdr->w7, FW_HDR_V1_W7_DYN_HDR);
>         info->idmem_share_mode = le32_get_bits(fw_hdr->w7, FW_HDR_V1_W7_IDMEM_SHARE_MODE);
> 
> --
> 2.51.2


  reply	other threads:[~2026-08-25  3:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-22  8:00 [PATCH] wifi: rtw89: cap firmware section_num before parsing Laxman Acharya Padhya
2026-08-25  3:54 ` Ping-Ke Shih [this message]
2026-08-25 17:44   ` [PATCH v2] " Laxman Acharya Padhya

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=26bf80f23bfa4fe49183d1f724fffc5c@realtek.com \
    --to=pkshih@realtek.com \
    --cc=acharyalaxman8848@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=stable@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