CVE-2026-68403
Last modified
CVE-2026-68403 is a vulnerability of currently unknown severity. 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.
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.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 9982464379e81ece51ced03ebecbbcd34ea367a6, < f50a2b9e57a751e70ae9a272875d80d39eaccd6a; >= 9982464379e81ece51ced03ebecbbcd34ea367a6, < 6bd21ec8549a5854dd64204a66289952917a924c; >= 9982464379e81ece51ced03ebecbbcd34ea367a6, < 5c342437ea44bb829680ca9e4f683dd5b325b219; >= 9982464379e81ece51ced03ebecbbcd34ea367a6, < c73c3fc1c7ca5a927639f0884624cb244ba791e4; >= 9982464379e81ece51ced03ebecbbcd34ea367a6, < 2a665946e0407a05a3f81bd56a08553c446498e0 |
| Linux | Linux | 4.1 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-68403?
How severe is CVE-2026-68403?
How do I fix CVE-2026-68403?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-68398In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68399In the Linux kernel, the following vulnerability has been re…
- CVE-2026-6840Missing bounds validation for operator could allow out of r…5.5
- CVE-2026-68400In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68401In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68402In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68404In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68405In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68406In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68407In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68408In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68409In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-68403?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
