From: Tristan Madani <tristmd@gmail.com>
To: Brian Norris <briannorris@chromium.org>,
Francesco Dolcini <francesco@dolcini.it>
Cc: linux-wireless@vger.kernel.org, stable@vger.kernel.org,
Tristan Madani <tristan@talencesecurity.com>
Subject: [PATCH wireless 0/3] wifi: mwifiex: firmware response validation fixes
Date: Sun, 1 Nov 2026 20:57:59 +0000 [thread overview]
Message-ID: <20261101205802.2909524-1-tristmd@gmail.com> (raw)
From: Tristan Madani <tristan@talencesecurity.com>
Three input validation fixes for the mwifiex driver:
1/3: The ADDBA response handler uses a 4-bit TID value (0-15) to
index an 8-entry array. Values >= 8 result in out-of-bounds
array access.
2/3: The multichannel event handler uses intf_num from a TLV to
iterate a flexible array without checking it fits the TLV
data.
3/3: The IBSS connected event handler replaces a buffer-bounded
length with the TLV header length, which may exceed the
event buffer.
Tristan Madani (3):
wifi: mwifiex: validate TID in ADDBA response handler
wifi: mwifiex: validate intf_num in multichannel event handler
wifi: mwifiex: cap TLV length in IBSS connected event handler
drivers/net/wireless/marvell/mwifiex/11n.c | 6 ++++++
drivers/net/wireless/marvell/mwifiex/sta_event.c | 6 ++++++
2 files changed, 12 insertions(+)
--
2.47.3
next reply other threads:[~2026-11-01 20:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-01 20:57 Tristan Madani [this message]
2026-11-01 20:58 ` [PATCH wireless 1/3] wifi: mwifiex: validate TID in ADDBA response handler Tristan Madani
2026-11-01 20:58 ` [PATCH wireless 2/3] wifi: mwifiex: validate intf_num in multichannel event handler Tristan Madani
2026-11-01 20:58 ` [PATCH wireless 3/3] wifi: mwifiex: cap TLV length in IBSS connected " Tristan Madani
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=20261101205802.2909524-1-tristmd@gmail.com \
--to=tristmd@gmail.com \
--cc=briannorris@chromium.org \
--cc=francesco@dolcini.it \
--cc=linux-wireless@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tristan@talencesecurity.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