CVE-2026-68403
wifi: brcmfmac: initialize SDIO data work before cleanup
In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: initialize SDIO data work before cleanup brcmf_sdio_probe() stores the newly allocated bus in sdiodev->bus before allocating the ordered workqueue. If that allocation fails, the function jumps to fail and calls brcmf_sdio_remove(). brcmf_sdio_remove() unconditionally cancels bus->datawork. Initialize the work item before the first failure path that can reach brcmf_sdio_remove(), so the cleanup path always observes a valid work object. This issue was found by our static analysis tool and then confirmed by manual review of the probe error path and the remove-time work drain. The problem pattern is an early setup failure that reaches a cleanup helper which cancels an embedded work item before its initializer has run. A QEMU PoC forced alloc_ordered_workqueue() to fail at the same point in brcmf_sdio_probe(), before INIT_WORK(&bus->datawork) is reached. The resulting fail path calls brcmf_sdio_remove(), and DEBUG_OBJECTS reports the invalid work drain with brcmf_sdio_probe() and brcmf_sdio_remove() in the stack.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Linux Linux |
≥ 9982464379e81ece51ced03ebecbbcd34ea367a6; < 860887d22890417d43ef8298f0cc4865e29b54de (affected, git) ≥ 9982464379e81ece51ced03ebecbbcd34ea367a6; < 9a4be91e5bb032b34cb3c962f6d4f82e7ef09364 (affected, git) ≥ 9982464379e81ece51ced03ebecbbcd34ea367a6; < fb12c87ae855346321af72e57a93c146205f1090 (affected, git) ≥ 9982464379e81ece51ced03ebecbbcd34ea367a6; < f50a2b9e57a751e70ae9a272875d80d39eaccd6a (affected, git) ≥ 9982464379e81ece51ced03ebecbbcd34ea367a6; < 6bd21ec8549a5854dd64204a66289952917a924c (affected, git) ≥ 9982464379e81ece51ced03ebecbbcd34ea367a6; < 5c342437ea44bb829680ca9e4f683dd5b325b219 (affected, git) ≥ 9982464379e81ece51ced03ebecbbcd34ea367a6; < c73c3fc1c7ca5a927639f0884624cb244ba791e4 (affected, git) ≥ 9982464379e81ece51ced03ebecbbcd34ea367a6; < 2a665946e0407a05a3f81bd56a08553c446498e0 (affected, git) Other versions: unaffected |
CNA: Linux |
| Linux Linux |
4.1 (affected) ≥ 0; < 4.1 (unaffected, semver) ≥ 5.10.265; ≤ 5.10.* (unaffected, semver) ≥ 5.15.216; ≤ 5.15.* (unaffected, semver) ≥ 6.1.183; ≤ 6.1.* (unaffected, semver) ≥ 6.6.148; ≤ 6.6.* (unaffected, semver) ≥ 6.12.101; ≤ 6.12.* (unaffected, semver) ≥ 6.18.42; ≤ 6.18.* (unaffected, semver) ≥ 7.1.6; ≤ 7.1.* (unaffected, semver) ≥ 7.2; ≤ * (unaffected, original_commit_for_fix) Other versions: affected |
CNA: Linux |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
No CVSS assessment reported. An unscored record is not a low-severity determination.
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://git.kernel.org/stable/c/860887d22890417d43ef8298f0cc4865e29b54deCNA: Linux
- https://git.kernel.org/stable/c/9a4be91e5bb032b34cb3c962f6d4f82e7ef09364CNA: Linux
- https://git.kernel.org/stable/c/fb12c87ae855346321af72e57a93c146205f1090CNA: Linux
- https://git.kernel.org/stable/c/f50a2b9e57a751e70ae9a272875d80d39eaccd6aCNA: Linux
- https://git.kernel.org/stable/c/6bd21ec8549a5854dd64204a66289952917a924cCNA: Linux
- https://git.kernel.org/stable/c/5c342437ea44bb829680ca9e4f683dd5b325b219CNA: Linux
- https://git.kernel.org/stable/c/c73c3fc1c7ca5a927639f0884624cb244ba791e4CNA: Linux
- https://git.kernel.org/stable/c/2a665946e0407a05a3f81bd56a08553c446498e0CNA: Linux
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.