From: Andreas Wendleder <gonsolo@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: johannes@sipsolutions.net, b43-dev@lists.infradead.org,
m@bues.ch, alessio.ferri@mythread.it
Subject: Re: [PATCH] wifi: b43: fix use-after-free in b43_bcma_remove()
Date: Tue, 13 Oct 2026 02:16:04 +0200 [thread overview]
Message-ID: <20261013001604.49954-1-gonsolo@gmail.com> (raw)
In-Reply-To: <20261013000124.48605-1-gonsolo@gmail.com>
Adding the people the CI bot listed as not CCed (b43 author and others
working on b43), for information. No changes to the patch.
The bug is in mainline: b43_bcma_remove() reads wldev->dev after
b43_one_core_detach() has freed wldev. b43_ssb_remove() already takes a
copy, so the patch does the same.
Andreas
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Wendleder <gonsolo@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: johannes@sipsolutions.net, b43-dev@lists.infradead.org, m@bues.ch
Subject: Re: [PATCH] wifi: b43: fix use-after-free in b43_bcma_remove()
Date: Tue, 13 Oct 2026 02:16:04 +0200 [thread overview]
Message-ID: <20261013001604.49954-1-gonsolo@gmail.com> (raw)
In-Reply-To: <20261013000124.48605-1-gonsolo@gmail.com>
Adding the people the CI bot listed as not CCed (b43 author and others
working on b43), for information. No changes to the patch.
The bug is in mainline: b43_bcma_remove() reads wldev->dev after
b43_one_core_detach() has freed wldev. b43_ssb_remove() already takes a
copy, so the patch does the same.
Andreas
_______________________________________________
b43-dev mailing list
b43-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/b43-dev
next prev parent reply other threads:[~2026-10-13 0:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 0:01 [PATCH] wifi: b43: fix use-after-free in b43_bcma_remove() Andreas Wendleder
2026-10-13 0:01 ` Andreas Wendleder
2026-10-13 0:16 ` Andreas Wendleder [this message]
2026-10-13 0:16 ` Andreas Wendleder
2026-10-13 17:16 ` Michael Büsch
2026-10-13 17:16 ` 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=20261013001604.49954-1-gonsolo@gmail.com \
--to=gonsolo@gmail.com \
--cc=alessio.ferri@mythread.it \
--cc=b43-dev@lists.infradead.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=m@bues.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.