From: Arend Van Spriel <aspriel@gmail.com>
To: Alexander Coffin <alex.coffin@matician.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>
Cc: linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
SHA-cyfmac-dev-list@infineon.com
Subject: Re: [PATCH] brcmfmac: fix use-after-free bug
Date: Mon, 8 Aug 2022 10:42:39 +0200 [thread overview]
Message-ID: <ff359bed-ddfa-9f18-e926-fad986b9918b@gmail.com> (raw)
In-Reply-To: <20220802172823.1696680-2-alex.coffin@matician.com>
On 8/2/2022 7:28 PM, Alexander Coffin wrote:
>
A commit message would have been nice...
> Signed-off-by: Alexander Coffin <alex.coffin@matician.com>
> ---
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/core.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/core.c b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/core.c
> index 87aef211b35f..12ee8b7163fd 100644
> --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/core.c
> +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/core.c
> @@ -296,6 +296,7 @@ static netdev_tx_t brcmf_netdev_start_xmit(struct sk_buff *skb,
> struct brcmf_pub *drvr = ifp->drvr;
> struct ethhdr *eh;
> int head_delta;
> + unsigned int tx_bytes = skb->len;
>
> brcmf_dbg(DATA, "Enter, bsscfgidx=%d\n", ifp->bsscfgidx);
>
> @@ -370,7 +371,7 @@ static netdev_tx_t brcmf_netdev_start_xmit(struct sk_buff *skb,
> ndev->stats.tx_dropped++;
> } else {
> ndev->stats.tx_packets++;
> - ndev->stats.tx_bytes += skb->len;
> + ndev->stats.tx_bytes += tx_bytes;
Why would this be a use-after-free? We only get here when ret is zero.
In that case the skb is not freed. If there would be a commit message
with some error report that proofs there is a use-after-free I would
look into this further, but now I just say NAK.
Regards,
Arend
> }
>
> /* Return ok: we always eat the packet */
next prev parent reply other threads:[~2022-08-08 8:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 17:28 brcmfmac: fix use-after-free bug Alexander Coffin
2022-08-02 17:28 ` [PATCH] " Alexander Coffin
2022-08-08 8:42 ` Arend Van Spriel [this message]
2022-08-08 9:38 ` Alexander Coffin
2022-08-08 12:10 ` Arend Van Spriel
2022-08-08 17:49 ` [PATCH v2] " Alexander Coffin
2022-08-12 15:05 ` Alexander Coffin
2022-08-13 18:24 ` Alexander Coffin
2022-09-07 7:57 ` [v2] wifi: brcmfmac: fix use-after-free bug in brcmf_netdev_start_xmit() 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=ff359bed-ddfa-9f18-e926-fad986b9918b@gmail.com \
--to=aspriel@gmail.com \
--cc=SHA-cyfmac-dev-list@infineon.com \
--cc=alex.coffin@matician.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--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