From: Jiale Yao <yaojiale02@163.com>
To: Jeff Johnson <jjohnson@kernel.org>, Kalle Valo <kvalo@kernel.org>,
Karthikeyan Periyasamy <quic_periyasa@quicinc.com>,
Maharaja Kennadyrajan <quic_mkenna@quicinc.com>,
Miles Hu <milehu@codeaurora.org>,
Sathishkumar Muruganandam <quic_murugana@quicinc.com>,
Carl Huang <quic_cjhuang@quicinc.com>,
Balamurugan Selvarajan <quic_bselvara@quicinc.com>,
Pradeep Kumar Chitrapu <quic_pradeepc@quicinc.com>,
Ramya Gnanasekar <quic_rgnanase@quicinc.com>,
Bhagavathi Perumal S <bperumal@codeaurora.org>,
Wen Gong <quic_wgong@quicinc.com>,
Aloka Dixit <quic_alokad@quicinc.com>,
linux-wireless@vger.kernel.org, ath11k@lists.infradead.org,
linux-kernel@vger.kernel.org, ath12k@lists.infradead.org
Subject: [PATCH 0/5] wifi: ath11k/ath12k: validate capability TLV lengths
Date: Wed, 28 Oct 2026 13:12:49 +0800 [thread overview]
Message-ID: <20261028051254.147628-1-yaojiale02@163.com> (raw)
Several ath11k and ath12k WMI parsers count firmware TLVs and later
consume them as arrays of complete capability structures. The generic
iterator validates that a TLV fits in its enclosing message, but these
tags have no minimum-length policies, so a short element can still cause
an out-of-bounds structure read.
Add policies for the DMA buffer release, hardware mode, DMA ring, and
extended MAC/PHY capability TLVs used by these paths.
Jiale Yao (5):
wifi: ath11k: validate DMA buffer release TLV lengths
wifi: ath11k: validate hardware mode capability TLVs
wifi: ath11k: validate DMA ring capability TLVs
wifi: ath12k: validate DMA buffer release fixed TLV length
wifi: ath12k: validate service-ready capability TLV lengths
drivers/net/wireless/ath/ath11k/wmi.c | 8 ++++++++
drivers/net/wireless/ath/ath12k/wmi.c | 8 ++++++++
2 files changed, 16 insertions(+)
--
2.34.1
next reply other threads:[~2026-10-28 5:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 5:12 Jiale Yao [this message]
2026-10-28 5:12 ` [PATCH 1/5] wifi: ath11k: validate DMA buffer release " Jiale Yao
2026-10-28 5:12 ` [PATCH 2/5] wifi: ath11k: validate hardware mode capability TLVs Jiale Yao
2026-10-28 5:12 ` [PATCH 3/5] wifi: ath11k: validate DMA ring " Jiale Yao
2026-10-28 5:12 ` [PATCH 4/5] wifi: ath12k: validate DMA buffer release fixed TLV length Jiale Yao
2026-10-28 5:12 ` [PATCH 5/5] wifi: ath12k: validate service-ready capability TLV 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=20261028051254.147628-1-yaojiale02@163.com \
--to=yaojiale02@163.com \
--cc=ath11k@lists.infradead.org \
--cc=ath12k@lists.infradead.org \
--cc=bperumal@codeaurora.org \
--cc=jjohnson@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=milehu@codeaurora.org \
--cc=quic_alokad@quicinc.com \
--cc=quic_bselvara@quicinc.com \
--cc=quic_cjhuang@quicinc.com \
--cc=quic_mkenna@quicinc.com \
--cc=quic_murugana@quicinc.com \
--cc=quic_periyasa@quicinc.com \
--cc=quic_pradeepc@quicinc.com \
--cc=quic_rgnanase@quicinc.com \
--cc=quic_wgong@quicinc.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®