CVE-2025-39863
- Source
- https://nvd.nist.gov/vuln/detail/CVE-2025-39863
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-39863.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2025-39863
- Downstream
- Related
- Published
- 2025-09-19T15:26:33Z
- Modified
- 2025-10-16T05:53:30.262088Z
- Summary
- wifi: brcmfmac: fix use-after-free when rescheduling brcmf_btcoex_info work
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
wifi: brcmfmac: fix use-after-free when rescheduling brcmfbtcoexinfo work
The brcmfbtcoexdetach() only shuts down the btcoex timer, if the flag timeron is false. However, the brcmfbtcoextimerfunc(), which runs as timer handler, sets timeron to false. This creates critical race conditions:
1.If brcmfbtcoexdetach() is called while brcmfbtcoextimerfunc() is executing, it may observe timeron as false and skip the call to timershutdown_sync().
2.The brcmfbtcoextimerfunc() may then reschedule the brcmfbtcoexinfo worker after the cancelworksync() has been executed, resulting in use-after-free bugs.
The use-after-free bugs occur in two distinct scenarios, depending on the timing of when the brcmfbtcoexinfo struct is freed relative to the execution of its worker thread.
Scenario 1: Freed before the worker is scheduled
The brcmfbtcoexinfo is deallocated before the worker is scheduled. A race condition can occur when schedulework(&btlocal->work) is called after the target memory has been freed. The sequence of events is detailed below:
CPU0 | CPU1 brcmfbtcoexdetach | brcmfbtcoextimerfunc | btlocal->timeron = false; if (cfg->btcoex->timeron) | ... | cancelworksync(); | ... | kfree(cfg->btcoex); // FREE | | schedulework(&bt_local->work); // USE
Scenario 2: Freed after the worker is scheduled
The brcmfbtcoexinfo is freed after the worker has been scheduled but before or during its execution. In this case, statements within the brcmfbtcoexhandler() — such as the containerof macro and subsequent dereferences of the brcmfbtcoex_info object will cause a use-after-free access. The following timeline illustrates this scenario:
CPU0 | CPU1 brcmfbtcoexdetach | brcmfbtcoextimerfunc | btlocal->timeron = false; if (cfg->btcoex->timeron) | ... | cancelworksync(); | ... | schedulework(); // Reschedule | kfree(cfg->btcoex); // FREE | brcmfbtcoexhandler() // Worker /* | btci = container_of(....); // USE The kfree() above could | ... also occur at any point | btci-> // USE during the worker's execution| */ |
To resolve the race conditions, drop the conditional check and call timershutdownsync() directly. It can deactivate the timer reliably, regardless of its current state. Once stopped, the timer_on state is then set to false.
- References
-
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- https://git.kernel.org/stable/c/2f6fbc8e04ca1d1d5c560be694199f847229c625
- https://git.kernel.org/stable/c/3e789f8475f6c857c88de5c5bf4b24b11a477dd7
- https://git.kernel.org/stable/c/9cb83d4be0b9b697eae93d321e0da999f9cdfcfc
- https://git.kernel.org/stable/c/f1150153c4e5940fe49ab51136343c5b4fe49d63
Affected packages
Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected ranges
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced61730d4dfffc2cc9d3a49fad87633008105c18baFixedf1150153c4e5940fe49ab51136343c5b4fe49d63
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced61730d4dfffc2cc9d3a49fad87633008105c18baFixed3e789f8475f6c857c88de5c5bf4b24b11a477dd7
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced61730d4dfffc2cc9d3a49fad87633008105c18baFixed2f6fbc8e04ca1d1d5c560be694199f847229c625
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced61730d4dfffc2cc9d3a49fad87633008105c18baFixed9cb83d4be0b9b697eae93d321e0da999f9cdfcfc