From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Jiale Yao <yaojiale02@163.com>,
Jeff Johnson <jjohnson@kernel.org>,
linux-wireless@vger.kernel.org, ath11k@lists.infradead.org,
ath12k@lists.infradead.org
Subject: Re: [PATCH 0/5] wifi: ath11k/ath12k: validate capability TLV lengths
Date: Wed, 28 Oct 2026 07:55:01 -0700 [thread overview]
Message-ID: <d7388ba1-926c-4a2c-b79b-0fcc0759d4d4@oss.qualcomm.com> (raw)
In-Reply-To: <20261028051254.147628-1-yaojiale02@163.com>
On 10/27/2026 10:12 PM, Jiale Yao wrote:
> 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(+)
>
-all codeaurora.org and quicinc.com e-mails since they no longer exist
In the future if you fix multiple drivers with one series, please send all
patches to all affected lists. Alternately, split into separate series, one
per driver.
It messes up my processing when a subset is sent to each list.
/jeff
next prev parent reply other threads:[~2026-10-28 14:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 5:12 [PATCH 0/5] wifi: ath11k/ath12k: validate capability TLV lengths Jiale Yao
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
2026-10-28 14:55 ` Jeff Johnson [this message]
2026-10-29 0:28 ` [PATCH 0/5] wifi: ath11k/ath12k: validate " Jeff Johnson
2026-10-29 4:20 ` 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=d7388ba1-926c-4a2c-b79b-0fcc0759d4d4@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=ath11k@lists.infradead.org \
--cc=ath12k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=yaojiale02@163.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