From: Kalle Valo <kvalo@codeaurora.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Amitkumar Karwar <amitkarwar@gmail.com>,
Ganapathi Bhat <ganapathi.bhat@nxp.com>,
Xinming Hu <huxinming820@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
"John W. Linville" <linville@tuxdriver.com>,
Bing Zhao <bzhao@marvell.com>,
Nishant Sarmukadam <nishants@marvell.com>,
Marc Yang <yangyang@marvell.com>,
Frank Huang <frankh@marvell.com>,
linux-wireless@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH net-next] mwifiex: Prevent memory corruption handling keys
Date: Wed, 15 Jul 2020 09:13:46 +0000 [thread overview]
Message-ID: <20200715091346.5FF4DC433A0@smtp.codeaurora.org> (raw)
In-Reply-To: <20200708115857.GA13729@mwanda>
Dan Carpenter <dan.carpenter@oracle.com> wrote:
> The length of the key comes from the network and it's a 16 bit number. It
> needs to be capped to prevent a buffer overflow.
>
> Fixes: 5e6e3a92b9a4 ("wireless: mwifiex: initial commit for Marvell mwifiex driver")
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> Acked-by: Ganapathi Bhat <ganapathi.bhat@nxp.com>
Patch applied to wireless-drivers-next.git, thanks.
e18696786548 mwifiex: Prevent memory corruption handling keys
--
https://patchwork.kernel.org/patch/11651443/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Amitkumar Karwar <amitkarwar@gmail.com>,
Ganapathi Bhat <ganapathi.bhat@nxp.com>,
Xinming Hu <huxinming820@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
"John W. Linville" <linville@tuxdriver.com>,
Bing Zhao <bzhao@marvell.com>,
Nishant Sarmukadam <nishants@marvell.com>,
Marc Yang <yangyang@marvell.com>,
Frank Huang <frankh@marvell.com>,
linux-wireless@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH net-next] mwifiex: Prevent memory corruption handling keys
Date: Wed, 15 Jul 2020 09:13:46 +0000 (UTC) [thread overview]
Message-ID: <20200715091346.5FF4DC433A0@smtp.codeaurora.org> (raw)
In-Reply-To: <20200708115857.GA13729@mwanda>
Dan Carpenter <dan.carpenter@oracle.com> wrote:
> The length of the key comes from the network and it's a 16 bit number. It
> needs to be capped to prevent a buffer overflow.
>
> Fixes: 5e6e3a92b9a4 ("wireless: mwifiex: initial commit for Marvell mwifiex driver")
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> Acked-by: Ganapathi Bhat <ganapathi.bhat@nxp.com>
Patch applied to wireless-drivers-next.git, thanks.
e18696786548 mwifiex: Prevent memory corruption handling keys
--
https://patchwork.kernel.org/patch/11651443/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-07-15 9:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 11:58 [PATCH net-next] mwifiex: Prevent memory corruption handling keys Dan Carpenter
2020-07-08 11:58 ` Dan Carpenter
2020-07-09 3:43 ` [EXT] " Ganapathi Bhat
2020-07-09 3:43 ` Ganapathi Bhat
2020-07-15 9:13 ` Kalle Valo [this message]
2020-07-15 9:13 ` Kalle Valo
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=20200715091346.5FF4DC433A0@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=amitkarwar@gmail.com \
--cc=bzhao@marvell.com \
--cc=dan.carpenter@oracle.com \
--cc=frankh@marvell.com \
--cc=ganapathi.bhat@nxp.com \
--cc=huxinming820@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=nishants@marvell.com \
--cc=yangyang@marvell.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.