Linux wireless drivers development
 help / color / mirror / Atom feed
From: Vasanthakumar Thiagarajan <vasanthakumar.thiagarajan@oss.qualcomm.com>
To: Tristan Madani <tristmd@gmail.com>,
	Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	Tristan Madani <tristan@talencesecurity.com>
Subject: Re: [PATCH v3 2/3] wifi: ath6kl: fix OOB read from firmware IE lengths in connect event
Date: Tue, 23 Jun 2026 13:15:15 +0530	[thread overview]
Message-ID: <be9cba58-e23d-4e39-94bb-343f22cee6a3@oss.qualcomm.com> (raw)
In-Reply-To: <20260421135009.348084-3-tristmd@gmail.com>



On 4/21/2026 7:20 PM, Tristan Madani wrote:
> From: Tristan Madani <tristan@talencesecurity.com>
> 
> The firmware-controlled beacon_ie_len, assoc_req_len, and assoc_resp_len
> fields in ath6kl_wmi_connect_event_rx() are not validated against the
> buffer length. Their sum (up to 765) can exceed the actual WMI event
> data, causing out-of-bounds reads during IE parsing and state corruption
> of wmi->is_wmm_enabled.
> 
> Add a check that the total IE length fits within the buffer.
> 
> Fixes: bdcd81707973 ("Add ath6kl cleaned up driver")
> Signed-off-by: Tristan Madani <tristan@talencesecurity.com>
> ---
> Changes in v3:
>    - Regenerated from wireless-next with proper git format-patch to
>      produce valid index hashes (v2 had post-processed index lines).
> 
> Changes in v2:
>    - No code changes from v1.
> 
>   drivers/net/wireless/ath/ath6kl/wmi.c | 8 ++++++++
>   1 file changed, 8 insertions(+)
> 
> diff --git a/drivers/net/wireless/ath/ath6kl/wmi.c b/drivers/net/wireless/ath/ath6kl/wmi.c
> index 72611a2ceb9d8..1cafbac2938fe 100644
> --- a/drivers/net/wireless/ath/ath6kl/wmi.c
> +++ b/drivers/net/wireless/ath/ath6kl/wmi.c
> @@ -862,6 +862,14 @@ static int ath6kl_wmi_connect_event_rx(struct wmi *wmi, u8 *datap, int len,
>   
>   	ev = (struct wmi_connect_event *) datap;
>   
> +	if (len < sizeof(*ev) + ev->beacon_ie_len +
> +	    ev->assoc_req_len + ev->assoc_resp_len) {
> +		ath6kl_dbg(ATH6KL_DBG_WMI,
> +			   "connect event: IE lengths %u+%u+%u exceed buffer %d\n",
> +			   ev->beacon_ie_len, ev->assoc_req_len,
> +			   ev->assoc_resp_len, len);
> +		return -EINVAL;
> +	}
>   	if (vif->nw_type == AP_NETWORK) {
>   		/* AP mode start/STA connected event */
>   		struct net_device *dev = vif->ndev;


Reviewed-by: Vasanthakumar Thiagarajan <vasanthakumar.thiagarajan@oss.qualcomm.com>

  reply	other threads:[~2026-06-23  7:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-21 13:50 [PATCH v3 0/3] wifi: ath6kl: firmware trust boundary hardening Tristan Madani
2026-04-21 13:50 ` [PATCH v3 1/3] wifi: ath6kl: fix OOB access from firmware ADDBA window size Tristan Madani
2026-06-23  7:10   ` Vasanthakumar Thiagarajan
2026-04-21 13:50 ` [PATCH v3 2/3] wifi: ath6kl: fix OOB read from firmware IE lengths in connect event Tristan Madani
2026-06-23  7:45   ` Vasanthakumar Thiagarajan [this message]
2026-04-21 13:50 ` [PATCH v3 3/3] wifi: ath6kl: fix OOB read from firmware num_msg in TX complete handler Tristan Madani
2026-06-18  2:26   ` Jeff Johnson

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=be9cba58-e23d-4e39-94bb-343f22cee6a3@oss.qualcomm.com \
    --to=vasanthakumar.thiagarajan@oss.qualcomm.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tristan@talencesecurity.com \
    --cc=tristmd@gmail.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