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>,
Mingyen Hsieh <mingyen.hsieh@mediatek.com>,
Quan Zhou <quan.zhou@mediatek.com>,
Deren Wu <deren.wu@mediatek.com>,
Leon Yen <leon.yen@mediatek.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Cc: stable@vger.kernel.org
Subject: [PATCH 2/3] wifi: mt76: mt7925: validate debug message lengths
Date: Wed, 28 Oct 2026 13:07:21 +0800 [thread overview]
Message-ID: <20261028050722.135598-3-yaojiale02@163.com> (raw)
In-Reply-To: <20261028050722.135598-1-yaojiale02@163.com>
The debug message event handler removes the event prefix and accesses the
message header without checking the skb length. It also subtracts the
fixed header from the firmware-provided length without checking for an
underflow and trusts the string length. A truncated event can therefore
cause out-of-bounds reads while formatting firmware logs.
Validate the event prefix, fixed fields, declared message extent and each
format-specific payload before reading them.
Fixes: c948b5da6bbe ("wifi: mt76: mt7925: add Mediatek Wi-Fi7 driver for mt7925 chips")
Cc: stable@vger.kernel.org
Signed-off-by: Jiale Yao <yaojiale02@163.com>
---
.../net/wireless/mediatek/mt76/mt7925/mcu.c | 24 +++++++++++++++++--
1 file changed, 22 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wireless/mediatek/mt76/mt7925/mcu.c b/drivers/net/wireless/mediatek/mt76/mt7925/mcu.c
index 26cdb3f0a98a..c612fda55eb7 100644
--- a/drivers/net/wireless/mediatek/mt76/mt7925/mcu.c
+++ b/drivers/net/wireless/mediatek/mt76/mt7925/mcu.c
@@ -596,8 +596,14 @@ mt7925_mcu_uni_debug_msg_event(struct mt792x_dev *dev, struct sk_buff *skb)
} __packed txt;
};
} __packed * hdr;
+ u16 msg_len;
+ if (skb->len < sizeof(struct mt7925_mcu_rxd) + 4)
+ return;
skb_pull(skb, sizeof(struct mt7925_mcu_rxd) + 4);
+ if (skb->len < offsetof(struct mt7925_uni_debug_msg, idx))
+ return;
+
hdr = (struct mt7925_uni_debug_msg *)skb->data;
if (hdr->id == 0x28) {
@@ -608,19 +614,28 @@ mt7925_mcu_uni_debug_msg_event(struct mt792x_dev *dev, struct sk_buff *skb)
return;
}
+ msg_len = le16_to_cpu(hdr->len);
+ if (msg_len < offsetof(struct mt7925_uni_debug_msg, idx) ||
+ msg_len > skb->len)
+ return;
+
if (hdr->type == 0) { /* idx log */
int i, ret, len = PAGE_SIZE - 1, nr_val;
- struct page *page = dev_alloc_pages(get_order(len));
+ struct page *page;
__le32 *val;
char *buf, *cur;
+ if (msg_len < sizeof(*hdr))
+ return;
+
+ page = dev_alloc_pages(get_order(len));
if (!page)
return;
buf = page_address(page);
cur = buf;
- nr_val = (le16_to_cpu(hdr->len) - sizeof(*hdr)) / 4;
+ nr_val = (msg_len - sizeof(*hdr)) / sizeof(*val);
val = (__le32 *)hdr->idx.data;
for (i = 0; i < nr_val && len > 0; i++) {
ret = snprintf(cur, len, "0x%x,", le32_to_cpu(val[i]));
@@ -635,6 +650,11 @@ mt7925_mcu_uni_debug_msg_event(struct mt792x_dev *dev, struct sk_buff *skb)
le32_to_cpu(hdr->idx.idx), nr_val, buf);
put_page(page);
} else if (hdr->type == 2) { /* str log */
+ if (msg_len < offsetof(struct mt7925_uni_debug_msg, txt.data) ||
+ hdr->txt.len > msg_len - offsetof(struct mt7925_uni_debug_msg,
+ txt.data))
+ return;
+
wiphy_info(mt76_hw(dev)->wiphy, "%.*s", hdr->txt.len, hdr->txt.data);
}
}
--
2.34.1
next prev parent 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 [PATCH 0/3] wifi: mt76: validate mt792x firmware TLV payloads Jiale Yao
2026-10-28 5:07 ` [PATCH 1/3] wifi: mt76: mt7921: validate NIC capability payload lengths Jiale Yao
2026-10-28 5:07 ` Jiale Yao [this message]
2026-10-28 5:07 ` [PATCH 3/3] wifi: mt76: mt7925: " 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-3-yaojiale02@163.com \
--to=yaojiale02@163.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=deren.wu@mediatek.com \
--cc=leon.yen@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=quan.zhou@mediatek.com \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shayne.chen@mediatek.com \
--cc=stable@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
all inboxes | Powered by JetHome®