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>,
Deren Wu <deren.wu@mediatek.com>,
Nelson Yu <nelson.yu@mediatek.com>,
Mingyen Hsieh <mingyen.hsieh@mediatek.com>,
Rong Yan <rong.yan@mediatek.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: [PATCH 0/3] wifi: mt76: validate mt792x firmware TLV payloads
Date: Wed, 28 Oct 2026 13:07:19 +0800 [thread overview]
Message-ID: <20261028050722.135598-1-yaojiale02@163.com> (raw)
The mt7921 and mt7925 firmware event parsers validate some outer skb
lengths, but several paths still trust type-specific lengths before
reading fixed fields. Malformed responses can make the drivers read past
a TLV payload, and a zero-length mt7925 capability TLV can stop progress
through the response.
Validate the fixed and type-specific payload extents before consuming
NIC capability and debug message data. Each patch covers one independent
parser and can be applied separately.
Jiale Yao (3):
wifi: mt76: mt7921: validate NIC capability payload lengths
wifi: mt76: mt7925: validate debug message lengths
wifi: mt76: mt7925: validate NIC capability payload lengths
.../net/wireless/mediatek/mt76/mt7921/mcu.c | 41 +++++++++---
.../net/wireless/mediatek/mt76/mt7925/mcu.c | 67 ++++++++++++++++---
2 files changed, 90 insertions(+), 18 deletions(-)
--
2.34.1
next reply other threads:[~2026-10-28 5:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 5:07 Jiale Yao [this message]
2026-10-28 5:07 ` [PATCH 1/3] wifi: mt76: mt7921: validate NIC capability payload lengths Jiale Yao
2026-10-28 5:07 ` [PATCH 2/3] wifi: mt76: mt7925: validate debug message lengths Jiale Yao
2026-10-28 5:07 ` [PATCH 3/3] wifi: mt76: mt7925: validate NIC capability payload lengths 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=20261028050722.135598-1-yaojiale02@163.com \
--to=yaojiale02@163.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=deren.wu@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=mingyen.hsieh@mediatek.com \
--cc=nbd@nbd.name \
--cc=nelson.yu@mediatek.com \
--cc=rong.yan@mediatek.com \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shayne.chen@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
all inboxes | Powered by JetHome®