Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Tianchu Chen" <tianchu.chen@linux.dev>
To: briannorris@chromium.org, francesco@dolcini.it
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wifi: mwifiex: bound SDIO fw dump count by memory table size
Date: Fri, 11 Sep 2026 07:18:09 +0000	[thread overview]
Message-ID: <c584533a7433cdcdd94c554621bb7d466854bd83@linux.dev> (raw)
In-Reply-To: <7d886d74276c05eeb1b1698e31b72a5aed98612a@linux.dev>

September 4, 2026 at 8:57 PM, "Tianchu Chen" <tianchu.chen@linux.dev mailto:tianchu.chen@linux.dev?to=%22Tianchu%20Chen%22%20%3Ctianchu.chen%40linux.dev%3E > wrote:


> 
> From: Tianchu Chen <flynnnchen@tencent.com>
> 
> mwifiex_sdio_fw_dump() reads the number of memory regions (dump_num) from 
> a device register and uses it to index the static 15-entry
> mem_type_mapping_tbl[] without any bounds check. A bogus device can
> report a dump_num larger than the table, making each loop iteration
> store a vmalloc pointer and a device-controlled size past the end
> of the table into adjacent .data (up to ~5.7KB when dump_num is 255).
> 
> The dump path runs after command timeouts or firmware crashes, so a
> bogus device can first force an error to trigger the dump and
> then report a bogus dump_num.
> 
> Aborting the dump only loses the firmware snapshot; the card reset 
> that follows is unaffected, so error recovery still completes.
> 
> Discovered by Atuin - Automated Vulnerability Discovery Engine.
> 
> Fixes: 54881c6b37c8d ("mwifiex: add firmware dump feature for SDIO")
> Cc: stable@vger.kernel.org
> Assisted-by: LLM
> Signed-off-by: Tianchu Chen <flynnnchen@tencent.com>
> ---
>  drivers/net/wireless/marvell/mwifiex/sdio.c | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/drivers/net/wireless/marvell/mwifiex/sdio.c b/drivers/net/wireless/marvell/mwifiex/sdio.c
> index f039d6f19183a..e40ca40418b30 100644
> --- a/drivers/net/wireless/marvell/mwifiex/sdio.c
> +++ b/drivers/net/wireless/marvell/mwifiex/sdio.c
> @@ -2795,6 +2795,11 @@ static void mwifiex_sdio_fw_dump(struct mwifiex_adapter *adapter)
>  mwifiex_dbg(adapter, ERROR, "SDIO read memory length err\n");
>  goto done;
>  }
> + if (dump_num > ARRAY_SIZE(mem_type_mapping_tbl)) {
> + mwifiex_dbg(adapter, ERROR,
> + "Invalid fw dump num: %d\n", dump_num);
> + goto done;
> + }
>  
>  /* Read the length of every memory which will dump */
>  for (idx = 0; idx < dump_num; idx++) {
> -- 
> 2.51.0
>

Hi,

I noticed that this patch is marked as "Changes Requested" in
Wireless Patchwork, but I haven't received any review comments.

Could you please point me to the requested changes or the relevant
review message? I am happy to send a v2 once I know what should be improved.

Best regards,

Tianchu

      reply	other threads:[~2026-09-11  7:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 12:57 [PATCH] wifi: mwifiex: bound SDIO fw dump count by memory table size Tianchu Chen
2026-09-11  7:18 ` Tianchu Chen [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=c584533a7433cdcdd94c554621bb7d466854bd83@linux.dev \
    --to=tianchu.chen@linux.dev \
    --cc=briannorris@chromium.org \
    --cc=francesco@dolcini.it \
    --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