All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Matthias Maennich <maennich@google.com>
Cc: stable@vger.kernel.org, kernel-team@android.com,
	qize wang <wangqize888888888@gmail.com>,
	Kalle Valo <kvalo@codeaurora.org>
Subject: Re: [PATCH 4.9] mwifiex: Fix heap overflow in mmwifiex_process_tdls_action_frame()
Date: Mon, 16 Mar 2020 15:12:25 +0100	[thread overview]
Message-ID: <20200316141225.GA4048369@kroah.com> (raw)
In-Reply-To: <20200316140851.7622-1-maennich@google.com>

On Mon, Mar 16, 2020 at 03:08:51PM +0100, Matthias Maennich wrote:
> From: qize wang <wangqize888888888@gmail.com>
> 
> mwifiex_process_tdls_action_frame() without checking
> the incoming tdls infomation element's vality before use it,
> this may cause multi heap buffer overflows.
> 
> Fix them by putting vality check before use it.
> 
> IE is TLV struct, but ht_cap and  ht_oper aren’t TLV struct.
> the origin marvell driver code is wrong:
> 
> memcpy(&sta_ptr->tdls_cap.ht_oper, pos,....
> memcpy((u8 *)&sta_ptr->tdls_cap.ht_capb, pos,...
> 
> Fix the bug by changing pos(the address of IE) to
> pos+2 ( the address of IE value ).
> 
> Signed-off-by: qize wang <wangqize888888888@gmail.com>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
> (cherry picked from commit 1e58252e334dc3f3756f424a157d1b7484464c40)
> Signed-off-by: Matthias Maennich <maennich@google.com>
> ---
>  drivers/net/wireless/marvell/mwifiex/tdls.c | 70 +++++++++++++++++++--
>  1 file changed, 64 insertions(+), 6 deletions(-)

Now queued up, thanks.

greg k-h

      reply	other threads:[~2020-03-16 14:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-16 14:08 [PATCH 4.9] mwifiex: Fix heap overflow in mmwifiex_process_tdls_action_frame() Matthias Maennich
2020-03-16 14:12 ` Greg KH [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=20200316141225.GA4048369@kroah.com \
    --to=greg@kroah.com \
    --cc=kernel-team@android.com \
    --cc=kvalo@codeaurora.org \
    --cc=maennich@google.com \
    --cc=stable@vger.kernel.org \
    --cc=wangqize888888888@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.