From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Duoming Zhou <duoming@zju.edu.cn>, brcm80211@lists.linux.dev
Cc: brcm80211-dev-list.pdl@broadcom.com,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
mingo@kernel.org, tglx@linutronix.de
Subject: Re: [PATCH] brcmfmac: btcoex: Fix use-after-free when rescheduling brcmf_btcoex_info work
Date: Thu, 21 Aug 2025 20:44:21 +0200 [thread overview]
Message-ID: <d071faf8-e800-4169-a670-8971d57b6997@broadcom.com> (raw)
In-Reply-To: <20250821043202.21263-1-duoming@zju.edu.cn>
On 8/21/2025 6:32 AM, Duoming Zhou wrote:
> The brcmf_btcoex_detach() only shuts down the btcoex timer, if the
> flag timer_on is false. However, the brcmf_btcoex_timerfunc(), which
> runs as timer handler, sets timer_on to false. This creates a critical
> race condition:
>
> 1.If brcmf_btcoex_detach() is called while brcmf_btcoex_timerfunc()
> is executing, it may observe timer_on as false and skip the call to
> timer_shutdown_sync().
>
> 2.The brcmf_btcoex_timerfunc() may then reschedule the brcmf_btcoex_info
> worker after the cancel_work_sync() has been executed.
>
> 3.Subsequently, the brcmf_btcoex_info structure is freed.
>
> 4.Finally, the rescheduled worker attempts to execute, leading to
> use-after-free bugs by accessing the freed brcmf_btcoex_info object.
Thanks for the patch. Being a nit picker just wanted to day that the
use-after-free happens a bit earlier as the worker itself is contained
in struct brcmf_btcoex_info. Also the diagram below does not add much
more than the textual description above.
> The following diagram illustrates this sequence of events:
>
> cpu0 cpu1
> brcmf_btcoex_detach | brcmf_btcoex_timerfunc
> | bt_local->timer_on = false;
> if (cfg->btcoex->timer_on) |
> ... |
> cancel_work_sync(); |
> ... | schedule_work() //reschedule
> kfree(cfg->btcoex);//free |
> | brcmf_btcoex_handler() //worker
> | btci-> //use
>
> To resolve this race condition, drop the conditional check and call
> timer_shutdown_sync() directly. It can deactivate the timer reliably,
> regardless of its current state. Once stopped, the timer_on state is
> then set to false.
However, no reason to stop this patch from going in so...
Acked-by: Arend van Spriel <arend.vanspriel@broadcom.com>
> Fixes: 61730d4dfffc ("brcmfmac: support critical protocol API for DHCP")
> Signed-off-by: Duoming Zhou <duoming@zju.edu.cn>
> ---
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/btcoex.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
next prev parent reply other threads:[~2025-08-21 18:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 4:32 Duoming Zhou
2025-08-21 18:44 ` Arend van Spriel [this message]
2025-08-22 4:15 ` duoming
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=d071faf8-e800-4169-a670-8971d57b6997@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=duoming@zju.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®