From: "Pali Rohár" <pali@kernel.org>
To: Ganapathi Bhat <ganapathi.bhat@nxp.com>
Cc: "Amitkumar Karwar" <amitkarwar@gmail.com>,
"Xinming Hu" <huxinming820@gmail.com>,
"Marek Behún" <marek.behun@nic.cz>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [EXT] mwifiex: Firmware name for W8997 sdio wifi chip
Date: Fri, 29 May 2020 10:46:30 +0200 [thread overview]
Message-ID: <20200529084630.j7rpdypt6vycsedh@pali> (raw)
In-Reply-To: <VI1PR04MB4366409B8E293A265851DA948F8F0@VI1PR04MB4366.eurprd04.prod.outlook.com>
On Friday 29 May 2020 08:43:56 Ganapathi Bhat wrote:
> Hi Pali,
>
> > According to publicly available information, firmware for these W8xxx
> > Marvell wifi chips is vulnerable to security issue CVE-2019-6496 [1].
> >
> > Are you able to update firmwares to the last versions and give us some
> > information which (old) firmware versions are affected by that security issue?
> >
> > So Linux distribution would know if they are distributing older vulnerable
> > firmwares and should push security fixes with new firmware versions.
> >
>
> 88W8787, 88W8797, 88W8801, 88W8897, and 88W8997 models are all already updated, with one exception:
> usb8897_uapsta.bin, which we will upstream soon;
Hello Ganapathi! Thank you for information. Can you point me to git tree
or location where are firmware files already updated?
next prev parent reply other threads:[~2020-05-29 8:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 13:23 mwifiex: Firmware name for W8997 sdio wifi chip Pali Rohár
2020-05-16 8:17 ` [EXT] " Ganapathi Bhat
2020-05-16 8:23 ` Pali Rohár
2020-05-28 10:34 ` Pali Rohár
2020-05-29 8:43 ` Ganapathi Bhat
2020-05-29 8:46 ` Pali Rohár [this message]
2020-05-29 8:49 ` Ganapathi Bhat
2020-05-29 8:55 ` Pali Rohár
2020-05-29 9:11 ` Ganapathi Bhat
2020-05-29 9:12 ` Pali Rohár
2020-06-18 12:36 ` Pali Rohár
2020-06-24 9:42 ` Ganapathi Bhat
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=20200529084630.j7rpdypt6vycsedh@pali \
--to=pali@kernel.org \
--cc=amitkarwar@gmail.com \
--cc=ganapathi.bhat@nxp.com \
--cc=huxinming820@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marek.behun@nic.cz \
/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;
as well as URLs for NNTP newsgroup(s).