From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless@vger.kernel.org,
Daniel J Blueman <daniel@quora.org>,
Arend van Spriel <arend.vanspriel@broadcom.com>
Subject: [PATCH for-4.11 0/2] brcmfmac: fixing use-after-free reports
Date: Tue, 28 Mar 2017 09:11:29 +0100 [thread overview]
Message-ID: <1490688691-20100-1-git-send-email-arend.vanspriel@broadcom.com> (raw)
Two use-after-free issues were found using KASAN and reported by
Daniel J Blueman. One of them was submitted as patch. However, no
response came upon my comments. So decided to push the fixes myself.
These patches are intended for v4.11 and apply to the master branch of
the wireless-drivers repository.
Arend van Spriel (2):
brcmfmac: use local iftype avoiding use-after-free of virtual
interface
cfg80211: check rdev resume callback only for registered wiphy
drivers/net/wireless/broadcom/brcm80211/brcmfmac/p2p.c | 8 +++++---
net/wireless/sysfs.c | 10 ++++------
2 files changed, 9 insertions(+), 9 deletions(-)
--
1.9.1
next reply other threads:[~2017-03-28 8:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 8:11 Arend van Spriel [this message]
2017-03-28 8:11 ` [PATCH for-4.11 1/2] brcmfmac: use local iftype avoiding use-after-free of virtual interface Arend van Spriel
2017-03-30 16:44 ` [for-4.11, " Kalle Valo
2017-03-28 8:11 ` [PATCH for-4.11 2/2] cfg80211: check rdev resume callback only for registered wiphy Arend van Spriel
2017-03-28 12:34 ` Johannes Berg
2017-03-28 14:13 ` Arend Van Spriel
2017-03-28 14:25 ` Johannes Berg
2017-03-28 14:46 ` Arend Van Spriel
2017-03-29 6:34 ` Johannes Berg
2017-03-29 7:13 ` Johannes Berg
2017-03-28 11:59 ` [PATCH for-4.11 0/2] brcmfmac: fixing use-after-free reports Kalle Valo
2017-03-28 14:08 ` Arend Van Spriel
2017-03-28 15:00 ` Kalle Valo
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=1490688691-20100-1-git-send-email-arend.vanspriel@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=daniel@quora.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@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).