Linux wireless drivers development
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Zheng Hacker <hackerzheng666@gmail.com>, Zheng Wang <zyytlz.wz@163.com>
Cc: "aspriel@gmail.com" <aspriel@gmail.com>,
	"franky.lin@broadcom.com" <franky.lin@broadcom.com>,
	"hante.meuleman@broadcom.com" <hante.meuleman@broadcom.com>,
	"kvalo@kernel.org" <kvalo@kernel.org>,
	"johannes.berg@intel.com" <johannes.berg@intel.com>,
	"marcan@marcan.st" <marcan@marcan.st>,
	"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
	"jisoo.jang@yonsei.ac.kr" <jisoo.jang@yonsei.ac.kr>,
	"linuxlovemin@yonsei.ac.kr" <linuxlovemin@yonsei.ac.kr>,
	"wataru.gohda@cypress.com" <wataru.gohda@cypress.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"brcm80211-dev-list.pdl@broadcom.com" 
	<brcm80211-dev-list.pdl@broadcom.com>,
	"SHA-cyfmac-dev-list@infineon.com"
	<SHA-cyfmac-dev-list@infineon.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"security@kernel.org" <security@kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: RE: [PATCH v3] brcmfmac: Fix use-after-free bug in brcmf_cfg80211_detach
Date: Mon, 6 Nov 2023 06:42:37 +0000	[thread overview]
Message-ID: <e783dbcedc9b444ca2651d2eac036d6e@realtek.com> (raw)
In-Reply-To: <CAJedcCxoDVS-7jVwLvsWOWiv0aObyYBiG-GmqX4bq+Qp+i3iTw@mail.gmail.com>



> -----Original Message-----
> From: Zheng Hacker <hackerzheng666@gmail.com>
> Sent: Monday, November 6, 2023 1:16 PM
> To: Zheng Wang <zyytlz.wz@163.com>
> Cc: aspriel@gmail.com; franky.lin@broadcom.com; hante.meuleman@broadcom.com; kvalo@kernel.org;
> johannes.berg@intel.com; marcan@marcan.st; linus.walleij@linaro.org; jisoo.jang@yonsei.ac.kr;
> linuxlovemin@yonsei.ac.kr; wataru.gohda@cypress.com; linux-wireless@vger.kernel.org;
> brcm80211-dev-list.pdl@broadcom.com; SHA-cyfmac-dev-list@infineon.com; linux-kernel@vger.kernel.org;
> security@kernel.org; stable@vger.kernel.org
> Subject: Re: [PATCH v3] brcmfmac: Fix use-after-free bug in brcmf_cfg80211_detach

subject prefix "wif: brcmfmac: ..."
Try "git log --oneline drivers/net/wireless/broadcom/brcm80211/brcmfmac" to know that. 

> 
> This is the candidate patch of CVE-2023-47233 :
> https://nvd.nist.gov/vuln/detail/CVE-2023-47233

I think you can add this link to commit message as well. 



  reply	other threads:[~2023-11-06  6:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06  4:39 [PATCH v3] brcmfmac: Fix use-after-free bug in brcmf_cfg80211_detach Zheng Wang
2023-11-06  5:16 ` Zheng Hacker
2023-11-06  6:42   ` Ping-Ke Shih [this message]
2023-11-06  6:52     ` Zheng Hacker

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=e783dbcedc9b444ca2651d2eac036d6e@realtek.com \
    --to=pkshih@realtek.com \
    --cc=SHA-cyfmac-dev-list@infineon.com \
    --cc=aspriel@gmail.com \
    --cc=brcm80211-dev-list.pdl@broadcom.com \
    --cc=franky.lin@broadcom.com \
    --cc=hackerzheng666@gmail.com \
    --cc=hante.meuleman@broadcom.com \
    --cc=jisoo.jang@yonsei.ac.kr \
    --cc=johannes.berg@intel.com \
    --cc=kvalo@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linuxlovemin@yonsei.ac.kr \
    --cc=marcan@marcan.st \
    --cc=security@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=wataru.gohda@cypress.com \
    --cc=zyytlz.wz@163.com \
    /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