From: Kalle Valo <kvalo@kernel.org>
To: Alex David <flu0r1ne@flu0r1ne.net>
Cc: ath11k@lists.infradead.org
Subject: Re: [PATCH] Change the max number of active probe SSIDs to match registration
Date: Mon, 07 Feb 2022 16:07:17 +0200 [thread overview]
Message-ID: <87o83ibwiy.fsf@kernel.org> (raw)
In-Reply-To: <YcRtS0oQyDNjCTQS@peregrine> (Alex David's message of "Thu, 23 Dec 2021 12:36:29 +0000")
Alex David <flu0r1ne@flu0r1ne.net> writes:
> The maximum number of SSIDs in a for active probe requests is currently
> reported as 16 (WLAN_SCAN_PARAMS_MAX_SSID) when registering the driver.
> The scan_req_params structure only has the capacity to hold 10 SSIDs.
> This leads to a buffer overflow which can be triggered from wpa_supplicant
> in userspace. When copying the SSIDs into the scan_req_params structure in
> the ath11k_mac_op_hw_scan route, it can overwrite the extraie pointer.
>
> Signed-off-by: Alex David <flu0r1ne@flu0r1ne.net>
I missed this as this wasn't in patchwork. This is because you didn't CC
linux-wireless. Please see instructions here how to submit ath11k
patches:
https://wireless.wiki.kernel.org/en/users/drivers/ath11k/submittingpatches
Please also add "ath11k:" prefix to the subject and a Tested-on tag.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
prev parent reply other threads:[~2022-02-07 14:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 12:36 [PATCH] Change the max number of active probe SSIDs to match registration Alex David
2022-02-07 14:07 ` Kalle Valo [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=87o83ibwiy.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=flu0r1ne@flu0r1ne.net \
/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