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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 9982464379e81ece51ced03ebecbbcd34ea367a6 and < 860887d22890417d43ef8298f0cc4865e29b54de≥ 9982464379e81ece51ced03ebecbbcd34ea367a6 and < 9a4be91e5bb032b34cb3c962f6d4f82e7ef09364≥ 9982464379e81ece51ced03ebecbbcd34ea367a6 and < fb12c87ae855346321af72e57a93c146205f1090≥ 9982464379e81ece51ced03ebecbbcd34ea367a6 and < f50a2b9e57a751e70ae9a272875d80d39eaccd6a≥ 9982464379e81ece51ced03ebecbbcd34ea367a6 and < 6bd21ec8549a5854dd64204a66289952917a924c≥ 9982464379e81ece51ced03ebecbbcd34ea367a6 and < 5c342437ea44bb829680ca9e4f683dd5b325b219≥ 9982464379e81ece51ced03ebecbbcd34ea367a6 and < c73c3fc1c7ca5a927639f0884624cb244ba791e4≥ 9982464379e81ece51ced03ebecbbcd34ea367a6 and < 2a665946e0407a05a3f81bd56a08553c446498e0 and 1 moreversion 4.1 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 30, 2026 · 15 reading(s) · max 0.18%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/c73c3fc1c7ca5a927639f0884624cb244ba791e4
- git.kernel.org/stable/c/f50a2b9e57a751e70ae9a272875d80d39eaccd6a
- git.kernel.org/stable/c/5c342437ea44bb829680ca9e4f683dd5b325b219
- git.kernel.org/stable/c/860887d22890417d43ef8298f0cc4865e29b54de
- git.kernel.org/stable/c/2a665946e0407a05a3f81bd56a08553c446498e0
- git.kernel.org/stable/c/fb12c87ae855346321af72e57a93c146205f1090
- git.kernel.org/stable/c/9a4be91e5bb032b34cb3c962f6d4f82e7ef09364
- git.kernel.org/stable/c/6bd21ec8549a5854dd64204a66289952917a924c
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 2d
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 2d
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 2d
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 2d
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 2d
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-68403 is "wifi: brcmfmac: initialize SDIO data work before cleanup", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.