CVE-2026-68403

wifi: brcmfmac: initialize SDIO data work before cleanup

N/A
Published: August 10, 2026 at 12:04 PM UTC
Updated: August 19, 2026 at 05:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.1 ≤ v < 5.10.2654.1 ≤ v < 5.15.2164.1 ≤ v < 6.1.1834.1 ≤ v < 6.12.1014.1 ≤ v < 6.18.424.1 ≤ v < 6.6.1484.1 ≤ v < 7.1.64.1 ≤ v < 7.24.19982464379e81ece51ced03ebecbbcd34ea367a6
Vendor states this is fixed in 2a665946e0407a05a3f81bd56a08553c446498e0 (fixed)
Vendor states this is fixed in 5c342437ea44bb829680ca9e4f683dd5b325b219 (fixed)
Vendor states this is fixed in 6bd21ec8549a5854dd64204a66289952917a924c (fixed)
Vendor states this is fixed in 860887d22890417d43ef8298f0cc4865e29b54de (fixed)
Vendor states this is fixed in 9a4be91e5bb032b34cb3c962f6d4f82e7ef09364 (fixed)
Vendor states this is fixed in c73c3fc1c7ca5a927639f0884624cb244ba791e4 (fixed)
Vendor states this is fixed in f50a2b9e57a751e70ae9a272875d80d39eaccd6a (fixed)
Vendor states this is fixed in fb12c87ae855346321af72e57a93c146205f1090 (fixed)
Vendor states this is fixed in 4.1 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card