From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Kees Cook <keescook@chromium.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: Gregory Greenman <gregory.greenman@intel.com>,
Kalle Valo <kvalo@kernel.org>,
Haim Dreyfuss <haim.dreyfuss@intel.com>,
Johannes Berg <johannes.berg@intel.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH v2] wifi: iwlwifi: mvm: Fix -Warray-bounds bug in iwl_mvm_wait_d3_notif()
Date: Tue, 6 Jun 2023 11:36:14 -0600 [thread overview]
Message-ID: <62ed7ac9-71bf-1fa5-1ae3-9c2060393b4b@embeddedor.com> (raw)
In-Reply-To: <202306051758.CD86F1E638@keescook>
On 6/5/23 19:03, Kees Cook wrote:
>>
>> Link: https://github.com/KSPP/linux/issues/306
>> Fixes: 905d50ddbc83 ("wifi: iwlwifi: mvm: support wowlan info notification version 2")
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Gustavo A. R. Silva <gustavoars@kernel.org>
>
> Nice catch!
(dancy-dance):D
,
>> if (wowlan_info_ver < 2) {
>> struct iwl_wowlan_info_notif_v1 *notif_v1 = (void *)pkt->data;
>>
>> - notif = kmemdup(notif_v1,
>> - offsetofend(struct iwl_wowlan_info_notif,
>> - received_beacons),
>> - GFP_ATOMIC);
>> -
>> + notif = kmemdup(notif_v1, sizeof(*notif), GFP_ATOMIC);
>
> The only question I have here is whether or not pkt->data actually
> contains sizeof(*notif)-many bytes? It seems the length isn't checked
> until after this area:
>
> len = iwl_rx_packet_payload_len(pkt);
>
> So, perhaps this needs to be changed instead, and the length
> double-checked, etc. Perhaps a regular kzalloc + memcpy is needed to
> handle pkt->data not being large enough?
As per Gregory's reply, it seems that the length is just fine.
Thanks
--
Gustavo
prev parent reply other threads:[~2023-06-06 17:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 19:42 Gustavo A. R. Silva
2023-06-06 1:03 ` Kees Cook
2023-06-06 9:09 ` Greenman, Gregory
2023-06-06 17:36 ` Gustavo A. R. Silva [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=62ed7ac9-71bf-1fa5-1ae3-9c2060393b4b@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=gregory.greenman@intel.com \
--cc=gustavoars@kernel.org \
--cc=haim.dreyfuss@intel.com \
--cc=johannes.berg@intel.com \
--cc=keescook@chromium.org \
--cc=kvalo@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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®