mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Greenman, Gregory" <gregory.greenman@intel.com>
To: "kvalo@kernel.org" <kvalo@kernel.org>,
	"Berg, Johannes" <johannes.berg@intel.com>,
	"christophe.jaillet@wanadoo.fr" <christophe.jaillet@wanadoo.fr>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"kernel-janitors@vger.kernel.org"
	<kernel-janitors@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH wireless] wifi: iwlwifi: mvm: Fix a memory corruption issue
Date: Mon, 28 Aug 2023 12:47:39 +0000	[thread overview]
Message-ID: <30c0426cfff334163d6b92f5255dd70ac44692c4.camel@intel.com> (raw)
In-Reply-To: <23f0ec986ef1529055f4f93dcb3940a6cf8d9a94.1690143750.git.christophe.jaillet@wanadoo.fr>

On Sun, 2023-07-23 at 22:24 +0200, Christophe JAILLET wrote:
> A few lines above, space is kzalloc()'ed for:
>         sizeof(struct iwl_nvm_data) +
>         sizeof(struct ieee80211_channel) +
>         sizeof(struct ieee80211_rate)
> 
> 'mvm->nvm_data' is a 'struct iwl_nvm_data', so it is fine.
> 
> At the end of this structure, there is the 'channels' flex array.
> Each element is of type 'struct ieee80211_channel'.
> So only 1 element is allocated in this array.
> 
> When doing:
>   mvm->nvm_data->bands[0].channels = mvm->nvm_data->channels;
> We point at the first element of the 'channels' flex array.
> So this is fine.
> 
> However, when doing:
>   mvm->nvm_data->bands[0].bitrates =
>                         (void *)((u8 *)mvm->nvm_data->channels + 1);
> because of the "(u8 *)" cast, we add only 1 to the address of the beginning
> of the flex array.
> 
> It is likely that we want point at the 'struct ieee80211_rate' allocated
> just after.
> 
> Remove the spurious casting so that the pointer arithmetic works as
> expected.
> 
> Fixes: 8ca151b568b6 ("iwlwifi: add the MVM driver")
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
> I've checked in the .s files, and :
> 
> Before
> ======
> # drivers/net/wireless/intel/iwlwifi/mvm/fw.c:801:              mvm->nvm_data->bands[0].channels = mvm->nvm_data->channels;
>         leaq    1448(%r13), %rax        #, tmp248
> 
> # drivers/net/wireless/intel/iwlwifi/mvm/fw.c:805:                      (void *)((u8 *)mvm->nvm_data->channels + 1);
>         leaq    1449(%r13), %rax        #, tmp252
> 
> 
> After:
> =====
> # drivers/net/wireless/intel/iwlwifi/mvm/fw.c:801:              mvm->nvm_data->bands[0].channels = mvm->nvm_data->channels;
>         leaq    1448(%r13), %rax        #, tmp248
> 
> # drivers/net/wireless/intel/iwlwifi/mvm/fw.c:805:                      (void *)(mvm->nvm_data->channels + 1);
>         leaq    1512(%r13), %rax        #, tmp252
> 
> And on my system sizeof(struct ieee80211_channel) = 64
> 
> /!\ This patch is only speculative and untested. /!\
> 
> It is strange that a memory corruption issue has been un-noticed for more
> than 10 years.
> 
> So review with care.
> ---
>  drivers/net/wireless/intel/iwlwifi/mvm/fw.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/net/wireless/intel/iwlwifi/mvm/fw.c b/drivers/net/wireless/intel/iwlwifi/mvm/fw.c
> index 1f5db65a088d..1d5ee4330f29 100644
> --- a/drivers/net/wireless/intel/iwlwifi/mvm/fw.c
> +++ b/drivers/net/wireless/intel/iwlwifi/mvm/fw.c

> @@ -802,7 +802,7 @@ int iwl_run_init_mvm_ucode(struct iwl_mvm *mvm)
>                 mvm->nvm_data->bands[0].n_channels = 1;
>                 mvm->nvm_data->bands[0].n_bitrates = 1;
>                 mvm->nvm_data->bands[0].bitrates =
> -                       (void *)((u8 *)mvm->nvm_data->channels + 1);
> +                       (void *)(mvm->nvm_data->channels + 1);
>                 mvm->nvm_data->bands[0].bitrates->hw_value = 10;
>         }
>  
Acked-by: Gregory Greenman <gregory.greenman@intel.com>


      reply	other threads:[~2023-08-28 12:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-23 20:24 Christophe JAILLET
2023-08-28 12:47 ` Greenman, Gregory [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=30c0426cfff334163d6b92f5255dd70ac44692c4.camel@intel.com \
    --to=gregory.greenman@intel.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=johannes.berg@intel.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=kvalo@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®