From: Hans de Goede <hdegoede@redhat.com>
To: Chi-Hsien Lin <chi-hsien.lin@cypress.com>,
Chirjeev Singh <Chirjeev.Singh@cypress.com>,
Chung-Hsien Hsu <cnhu@cypress.com>
Cc: linux-firmware@kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Updating cypress/brcm firmware in linux-firmware for CVE-2019-15126
Date: Wed, 26 Feb 2020 23:16:32 +0100 [thread overview]
Message-ID: <93dba8d2-6e46-9157-d292-4d93feb8ec1a@redhat.com> (raw)
Hello Cypress people,
Can we please get updated firmware for
brcm/brcmfmac4356-pcie.bin and brcm/brcmfmac4356-sdio.bin
fixing CVE-2019-15126 as well as for any other affected
models (the 4356 is explicitly named in the CVE description) ?
The current Cypress firmware files in linux-firmware are
quite old, e.g. for brcm/brcmfmac4356-pcie.bin linux-firmware has:
version 7.35.180.176 dated 2017-10-23, way before the CVE
Where as https://community.cypress.com/docs/DOC-19000 /
cypress-fmac-v4.14.77-2020_0115.zip has:
version 7.35.180.197 which presumably contains a fix (no changelog)
Regards,
Hans
next reply other threads:[~2020-02-26 22:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 22:16 Hans de Goede [this message]
2020-02-26 22:16 ` Updating cypress/brcm firmware in linux-firmware for CVE-2019-15126 Hans de Goede
2020-03-04 11:45 ` Hans de Goede
2020-03-04 11:45 ` Hans de Goede
2020-03-05 3:50 ` Chi-Hsien Lin
2020-03-05 3:50 ` Chi-Hsien Lin
2020-03-05 6:24 ` Hans de Goede
2020-03-05 6:24 ` Hans de Goede
2020-03-05 9:16 ` David Woodhouse
2020-03-05 9:16 ` David Woodhouse
2020-03-05 14:00 ` Hans de Goede
2020-03-05 14:00 ` Hans de Goede
2020-03-06 9:58 ` Chi-Hsien Lin
2020-03-06 9:58 ` Chi-Hsien Lin
2020-03-18 22:06 ` Hans de Goede
2020-03-18 22:06 ` Hans de Goede
2020-03-19 12:41 ` Hans de Goede
2020-03-19 12:41 ` Hans de Goede
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=93dba8d2-6e46-9157-d292-4d93feb8ec1a@redhat.com \
--to=hdegoede@redhat.com \
--cc=Chirjeev.Singh@cypress.com \
--cc=chi-hsien.lin@cypress.com \
--cc=cnhu@cypress.com \
--cc=linux-firmware@kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).