From: "Michael Büsch" <m@bues.ch>
To: b43-dev@lists.infradead.org
Subject: CVE-2017-9417 firmware fix with b43-fwcutter?
Date: Thu, 7 Sep 2017 20:54:25 +0200 [thread overview]
Message-ID: <20170907205107.6a3490f2@wiggum> (raw)
In-Reply-To: <1483001379.8665325.1504807495471.JavaMail.zimbra@redhat.com>
On Thu, 7 Sep 2017 14:04:55 -0400 (EDT)
Vladis Dronov <vdronov@redhat.com> wrote:
> I would join Drew in asking a question about CVE-2017-9417/Broadpwn.
> My main concern is if this flaw in a firmware above can affect
> laptop/desktop/server Linux systems?
>
> So far I see two contradicting answers: "he could reproduce the crash
> with the standard Linux firmware [on a mobile phone]" and "I do not
> think that Broadpwm is a problem". Can someone please clarify?
Mobile phones often use FullMAC chips.
That means the chip runs a small operating system and a full 802.11
MLME stack. Usually referred to as "firmware".
This is not to be confused with the "microcode" or "ucode". The ucode
runs on a small sequencer in the 802.11 baseband processor.
FullMAC: An ARM/MIPS core on the chip runs the 802.11 MLME stack.
The 802.11 baseband core runs ucode.
SoftMAC: The host system runs the 802.11 MLME stack.
The 802.11 baseband core runs ucode.
So if the vulnerability is in the "firmware" and not in the "ucode",
the SoftMAC chips are not affected.
--
Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20170907/79aa4ac6/attachment.sig>
prev parent reply other threads:[~2017-09-07 18:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 5:58 CVE-2017-9417 firmware fix with b43-fwcutter? Drew Scott Daniels
2017-09-06 7:15 ` Chris Bainbridge
2017-09-06 21:26 ` Larry Finger
2017-09-07 18:04 ` Vladis Dronov
2017-09-07 18:54 ` Michael Büsch [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=20170907205107.6a3490f2@wiggum \
--to=m@bues.ch \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).