From: Jiale Yao <yaojiale02@163.com>
To: Felix Fietkau <nbd@nbd.name>,
Lorenzo Bianconi <lorenzo@kernel.org>,
Ryder Lee <ryder.lee@mediatek.com>,
Shayne Chen <shayne.chen@mediatek.com>,
Sean Wang <sean.wang@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
YF Luo <yf.luo@mediatek.com>,
Chih-Min Chen <chih-min.chen@mediatek.com>,
Money Wang <Money.Wang@mediatek.com>,
MeiChia Chiu <meichia.chiu@mediatek.com>,
Bo Jiao <Bo.Jiao@mediatek.com>,
Peter Chiu <chui-hao.chiu@mediatek.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Cc: Jiale Yao <yaojiale02@163.com>
Subject: [PATCH 00/10] wifi: mt76: validate legacy MCU responses
Date: Mon, 19 Oct 2026 18:14:55 +0800 [thread overview]
Message-ID: <20261019101506.1926943-1-yaojiale02@163.com> (raw)
Several mt7603, mt7615, and mt7915 MCU response paths trust firmware
response sizes before reading receive descriptors, fixed fields, or
arrays. A truncated response can therefore cause an out-of-bounds read.
Validate the common response descriptors and each command-specific
payload before accessing or removing data from the skb.
Jiale Yao (10):
wifi: mt76: mt7603: validate MCU response length
wifi: mt76: mt7615: validate MCU response lengths
wifi: mt76: mt7915: validate MCU response lengths
wifi: mt76: mt7915: validate MURU statistics response
wifi: mt76: mt7915: validate EEPROM response length
wifi: mt76: mt7915: validate free-block response length
wifi: mt76: mt7915: validate channel MIB response length
wifi: mt76: mt7915: validate RX rate response length
wifi: mt76: mt7915: validate WED TX statistics response
wifi: mt76: mt7915: validate RF register response length
.../net/wireless/mediatek/mt76/mt7603/mcu.c | 2 +
.../net/wireless/mediatek/mt76/mt7615/mcu.c | 17 ++++++++
.../net/wireless/mediatek/mt76/mt7915/mcu.c | 43 +++++++++++++++++--
3 files changed, 59 insertions(+), 3 deletions(-)
--
2.34.1
next reply other threads:[~2026-10-19 10:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 10:14 Jiale Yao [this message]
2026-10-19 10:14 ` [PATCH 01/10] wifi: mt76: mt7603: validate MCU response length Jiale Yao
2026-10-19 10:14 ` [PATCH 02/10] wifi: mt76: mt7615: validate MCU response lengths Jiale Yao
2026-10-19 10:14 ` [PATCH 03/10] wifi: mt76: mt7915: " Jiale Yao
2026-10-19 10:14 ` [PATCH 04/10] wifi: mt76: mt7915: validate MURU statistics response Jiale Yao
2026-10-19 10:15 ` [PATCH 05/10] wifi: mt76: mt7915: validate EEPROM response length Jiale Yao
2026-10-19 10:15 ` [PATCH 06/10] wifi: mt76: mt7915: validate free-block " Jiale Yao
2026-10-19 10:15 ` [PATCH 07/10] wifi: mt76: mt7915: validate channel MIB " Jiale Yao
2026-10-19 10:15 ` [PATCH 08/10] wifi: mt76: mt7915: validate RX rate " Jiale Yao
2026-10-19 10:15 ` [PATCH 09/10] wifi: mt76: mt7915: validate WED TX statistics response Jiale Yao
2026-10-20 2:23 ` [PATCH 10/10] wifi: mt76: mt7915: validate RF register response length Jiale Yao
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=20261019101506.1926943-1-yaojiale02@163.com \
--to=yaojiale02@163.com \
--cc=Bo.Jiao@mediatek.com \
--cc=Money.Wang@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chih-min.chen@mediatek.com \
--cc=chui-hao.chiu@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=meichia.chiu@mediatek.com \
--cc=nbd@nbd.name \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shayne.chen@mediatek.com \
--cc=yf.luo@mediatek.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