From: Vladis Dronov <vdronov@redhat.com>
To: b43-dev@lists.infradead.org
Subject: CVE-2017-9417 firmware fix with b43-fwcutter?
Date: Thu, 7 Sep 2017 14:04:55 -0400 (EDT) [thread overview]
Message-ID: <1483001379.8665325.1504807495471.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20170906055818.GA25367@auburn.dreamhost.com>
Hello,
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?
I'm also trying to reach Broadcom guys via different channels with this
question, no reply for now.
Best regards,
Vladis Dronov | Red Hat, Inc. | Product Security Engineer
next prev parent reply other threads:[~2017-09-07 18:04 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 [this message]
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=1483001379.8665325.1504807495471.JavaMail.zimbra@redhat.com \
--to=vdronov@redhat.com \
--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