CVE-2025-39863wifi: brcmfmac: fix use-after-free when rescheduling brcmf_btcoex_info work
- 7.8HighCVSS base score
- 0.16%Exploitation in 30 daysEPSS · top 95% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: fix use-after-free when rescheduling brcmf_btcoex_info work 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 critical race conditions: 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, resulting in use-after-free bugs. The use-after-free bugs occur in two distinct scenarios, depending on the timing of when the brcmf_btcoex_info struct is freed relative to the execution of its worker thread. Scenario 1: Freed before the worker is scheduled The brcmf_btcoex_info is deallocated before the worker is scheduled. A race condition can occur when schedule_work(&bt_local->work) is called after the target memory has been freed. The sequence of events is detailed below: CPU0 | CPU1 brcmf_btcoex_detach | brcmf_btcoex_timerfunc | bt_local->timer_on = false; if (cfg->btcoex->timer_on) | ... | cancel_work_sync(); | ... | kfree(cfg->btcoex); // FREE | | schedule_work(&bt_local->work); // USE Scenario 2: Freed after the worker is scheduled The brcmf_btcoex_info is freed after the worker has been scheduled but before or during its execution. In this case, statements within the brcmf_btcoex_handler() — such as the container_of macro and subsequent dereferences of the brcmf_btcoex_info object will cause a use-after-free access. The following timeline illustrates this scenario: 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 = 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 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.
Timeline
ID reserved
By Linux
- 5 months later
· 5 months later
Published
- 13 months later
· 13 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| CISA-ADPADP (enrichment) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.16% · top 95% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 61730d4dfffc2cc9d3a49fad87633008105c18ba – < c75600e69e66a751cc046cd9c407b942f298d852
- affected 61730d4dfffc2cc9d3a49fad87633008105c18ba – < ae58f70bde0433f27ef4b388ab50634736607bf6
- affected 61730d4dfffc2cc9d3a49fad87633008105c18ba – < f1150153c4e5940fe49ab51136343c5b4fe49d63
- affected 61730d4dfffc2cc9d3a49fad87633008105c18ba – < 3e789f8475f6c857c88de5c5bf4b24b11a477dd7
- affected 61730d4dfffc2cc9d3a49fad87633008105c18ba – < 2f6fbc8e04ca1d1d5c560be694199f847229c625
- affected 61730d4dfffc2cc9d3a49fad87633008105c18ba – < 9cb83d4be0b9b697eae93d321e0da999f9cdfcfc
- affected 3.10
- unaffected < 3.10
- unaffected 5.15.210 – ≤ 5.15.*
- unaffected 6.1.167 – ≤ 6.1.*
- unaffected 6.6.105 – ≤ 6.6.*
- unaffected 6.12.46 – ≤ 6.12.*
- unaffected 6.16.6 – ≤ 6.16.*
- unaffected 6.17 – ≤ *
References
References7
- https://git.kernel.org/stable/c/c75600e69e66a751cc046cd9c407b942f298d852 (opens in a new tab)
- https://git.kernel.org/stable/c/ae58f70bde0433f27ef4b388ab50634736607bf6 (opens in a new tab)
- https://git.kernel.org/stable/c/f1150153c4e5940fe49ab51136343c5b4fe49d63 (opens in a new tab)
- https://git.kernel.org/stable/c/3e789f8475f6c857c88de5c5bf4b24b11a477dd7 (opens in a new tab)
- https://git.kernel.org/stable/c/2f6fbc8e04ca1d1d5c560be694199f847229c625 (opens in a new tab)
- https://git.kernel.org/stable/c/9cb83d4be0b9b697eae93d321e0da999f9cdfcfc (opens in a new tab)
- https://cert-portal.siemens.com/productcert/html/ssa-784472.html (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-30337 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-39863)Record last updated .