mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "jiale yao" <19888972804@163.com>
To: "Jeff Johnson" <jjohnson@kernel.org>,
	"Manikanta Pubbisetty" <quic_mpubbise@quicinc.com>,
	"Sathishkumar Muruganandam" <quic_murugana@quicinc.com>,
	"Anilkumar Kolli" <quic_akolli@quicinc.com>,
	"John Crispin" <john@phrozen.org>,
	"Kalle Valo" <kvalo@kernel.org>,
	"P Praneesh" <quic_ppranees@quicinc.com>,
	"Balamurugan Selvarajan" <quic_bselvara@quicinc.com>,
	"Karthikeyan Periyasamy" <quic_periyasa@quicinc.com>,
	"Vasanthakumar Thiagarajan" <quic_vthiagar@quicinc.com>,
	linux-wireless@vger.kernel.org, ath11k@lists.infradead.org,
	linux-kernel@vger.kernel.org, ath12k@lists.infradead.org
Cc: "Jiale Yao" <jiale.yao@example.com>
Subject: Re:[PATCH 0/4] wifi: ath11k/ath12k: validate firmware array lengths
Date: Tue, 20 Oct 2026 10:19:59 +0800 (CST)	[thread overview]
Message-ID: <b573b6f.2196.1a1571bc45e.Coremail.19888972804@163.com> (raw)
In-Reply-To: <20261019100029.1908660-1-yaojiale02@163.com>

This patch series is superseded — please ignore it due to the incorrect sender name.
New one is https://lore.kernel.org/lkml/20261019100506.1915181-1-yaojiale02@163.com
At 2026-10-19 18:00:25, "Jiale Yao" <yaojiale02@163.com> wrote:
>From: Jiale Yao <jiale.yao@example.com>
>
>ath11k and ath12k consume two firmware-provided arrays without fully
>validating their lengths. The service-ready-ext parser accepts fewer
>extended regulatory capability entries than the separately reported PHY
>count, while the ready-event parser trusts the reported extra MAC address
>count without checking the fixed-structure array length.
>
>Malformed firmware data can therefore make both drivers read beyond the
>corresponding TLV arrays. Add matching validation to each driver before
>the arrays are indexed.
>
>The four patches are independent and each addresses one parsing path in
>one driver.
>
>Jiale Yao (4):
>  wifi: ath11k: validate extended regulatory capability count
>  wifi: ath12k: validate extended regulatory capability count
>  wifi: ath11k: validate ready event MAC address array length
>  wifi: ath12k: validate ready event MAC address array length
>
> drivers/net/wireless/ath/ath11k/wmi.c | 10 ++++++++++
> drivers/net/wireless/ath/ath12k/wmi.c | 10 ++++++++++
> 2 files changed, 20 insertions(+)
>
>-- 
>2.34.1

      parent reply	other threads:[~2026-10-20  2:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19 10:00 [PATCH " Jiale Yao
2026-10-19 10:00 ` [PATCH 1/4] wifi: ath11k: validate extended regulatory capability count Jiale Yao
2026-10-19 10:00 ` [PATCH 2/4] wifi: ath12k: " Jiale Yao
2026-10-19 10:00 ` [PATCH 3/4] wifi: ath11k: validate ready event MAC address array length Jiale Yao
2026-10-19 10:00 ` [PATCH 4/4] wifi: ath12k: " Jiale Yao
2026-10-20  2:19 ` jiale yao [this message]

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=b573b6f.2196.1a1571bc45e.Coremail.19888972804@163.com \
    --to=19888972804@163.com \
    --cc=ath11k@lists.infradead.org \
    --cc=ath12k@lists.infradead.org \
    --cc=jiale.yao@example.com \
    --cc=jjohnson@kernel.org \
    --cc=john@phrozen.org \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_akolli@quicinc.com \
    --cc=quic_bselvara@quicinc.com \
    --cc=quic_mpubbise@quicinc.com \
    --cc=quic_murugana@quicinc.com \
    --cc=quic_periyasa@quicinc.com \
    --cc=quic_ppranees@quicinc.com \
    --cc=quic_vthiagar@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®