From: Tristan Madani <tristmd@gmail.com>
To: Jeff Chen <jeff.chen_1@nxp.com>
Cc: Francesco Dolcini <francesco@dolcini.it>,
Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Tristan Madani <tristan@talencesecurity.com>
Subject: [PATCH wireless 0/3] wifi: nxpwifi: validate firmware response sizes
Date: Mon, 2 Nov 2026 12:48:51 +0000 [thread overview]
Message-ID: <20261102124854.325979-1-tristmd@gmail.com> (raw)
From: Tristan Madani <tristan@talencesecurity.com>
nxpwifi inherits several patterns from mwifiex where firmware-provided
lengths and counts are used to bound loops and copies without
validation against the actual response buffer size. A malformed
firmware response can cause reads past the buffer.
This series adds bounds checks to three such paths:
1/3 - HE capability TLV length in 11ax config response
2/3 - ext_scan buf_size against event buffer length
3/3 - command response size against response skb length
All three were introduced with the driver in 73b01e57ed3e ("wifi: nxp:
add nxpwifi driver for IW61x").
Tristan Madani (3):
wifi: nxpwifi: validate HE capability TLV length in firmware response
wifi: nxpwifi: validate ext_scan buf_size against event buffer length
wifi: nxpwifi: validate command response size against buffer length
drivers/net/wireless/nxp/nxpwifi/11ax.c | 3 +++
drivers/net/wireless/nxp/nxpwifi/scan.c | 9 +++++++++
drivers/net/wireless/nxp/nxpwifi/cmdevt.c | 14 ++++++++++++++
3 files changed, 26 insertions(+)
--
2.47.3
next reply other threads:[~2026-11-02 12:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 12:48 Tristan Madani [this message]
2026-11-02 12:48 ` [PATCH wireless 1/3] wifi: nxpwifi: validate HE capability TLV length in firmware response Tristan Madani
2026-11-02 12:48 ` [PATCH wireless 2/3] wifi: nxpwifi: validate ext_scan buf_size against event buffer length Tristan Madani
2026-11-02 12:48 ` [PATCH wireless 3/3] wifi: nxpwifi: validate command response size against " 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=20261102124854.325979-1-tristmd@gmail.com \
--to=tristmd@gmail.com \
--cc=francesco@dolcini.it \
--cc=jeff.chen_1@nxp.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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
all inboxes | Powered by JetHome®