From: Drew Scott Daniels <ddaniels@UMAlumni.mb.ca>
To: b43-dev@lists.infradead.org
Subject: CVE-2017-9417 firmware fix with b43-fwcutter?
Date: Tue, 5 Sep 2017 22:58:18 -0700 [thread overview]
Message-ID: <20170906055818.GA25367@auburn.dreamhost.com> (raw)
Hi,
Is there newer firmware that fixes the CVE-2017-9417 vulnerability or does
it not apply to devices supported by this driver? If there is a different
CVE not released you can say that this doesn't apply. Is there newer
firmware in pre-release (e.g. brcmfw_170808.tgz)or is that firmware
unrelated (e.g. just for the BCM43430 that isn't listed as supported)?
https://blog.exodusintel.com/2017/07/26/broadpwn/ indicates the
vulnerabilities are focused in HardMAC and seems to imply that SoftMAC isn't
vulnerable (at least on the firmware side as the vulnerability is in the MAC
code). The models listed as affected on that site are BCM4339 through
BCM4361 though it seems others may be affected.
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1713276 says:
Cypress (was Broadcom) have given the Raspberry Pi foundation new releases
of the WiFi and Bluetooth firmware to fix the problem. See
https://github.com/raspberrypi/linux/issues/1342#issuecomment-321221748
Debian is tracking a related bug at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869639
Thanks,
Drew Daniels
Blog: http://www.boxheap.net/ddaniels/blog
next reply other threads:[~2017-09-06 5:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 5:58 Drew Scott Daniels [this message]
2017-09-06 7:15 ` CVE-2017-9417 firmware fix with b43-fwcutter? Chris Bainbridge
2017-09-06 21:26 ` Larry Finger
2017-09-07 18:04 ` Vladis Dronov
2017-09-07 18:54 ` Michael Büsch
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=20170906055818.GA25367@auburn.dreamhost.com \
--to=ddaniels@umalumni.mb.ca \
--cc=b43-dev@lists.infradead.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