wifi: brcmfmac: initialize SDIO data work before cleanup
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 2a665946e0407a05a3f81bd56a08553c446498e0, 5c342437ea44bb829680ca9e4f683dd5b325b219, 6bd21ec8549a5854dd64204a66289952917a924c; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 2a665946e0407a05a3f81bd56a08553c446498e0, 5c342437ea44bb829680ca9e4f683dd5b325b219, 6bd21ec8549a5854dd64204a66289952917a924c; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 10, 2026
- Updated
- Aug 19, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.1affected
- 9982464379e81ece51ced03ebecbbcd34ea367a6 and later · before 860887d22890417d43ef8298f0cc4865e29b54deaffected · git
- 9982464379e81ece51ced03ebecbbcd34ea367a6 and later · before 9a4be91e5bb032b34cb3c962f6d4f82e7ef09364affected · git
- 9982464379e81ece51ced03ebecbbcd34ea367a6 and later · before fb12c87ae855346321af72e57a93c146205f1090affected · git
- 9982464379e81ece51ced03ebecbbcd34ea367a6 and later · before f50a2b9e57a751e70ae9a272875d80d39eaccd6aaffected · git
- 9982464379e81ece51ced03ebecbbcd34ea367a6 and later · before 6bd21ec8549a5854dd64204a66289952917a924caffected · git
- 9982464379e81ece51ced03ebecbbcd34ea367a6 and later · before 5c342437ea44bb829680ca9e4f683dd5b325b219affected · git
- 9982464379e81ece51ced03ebecbbcd34ea367a6 and later · before c73c3fc1c7ca5a927639f0884624cb244ba791e4affected · git
- 9982464379e81ece51ced03ebecbbcd34ea367a6 and later · before 2a665946e0407a05a3f81bd56a08553c446498e0affected · git
- before 4.1not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.101-1~deb12u1 | 6.12.101-1~deb12u1 |
| Debian:13 | linux | before 6.12.101-1 | 6.12.101-1 |
| Debian:14 | linux | before 7.1.6-1 | 7.1.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-68392Aug 10, 2026 · Bluetooth: mgmt: fix locking in unpair_device/disconnect_sync31Monitor
- ← EarlierCVE-2026-68395Aug 10, 2026 · ata: sata_dwc_460ex: enable SATA interrupts only after IRQ handler is registered0Monitor
- Later →CVE-2026-68405Aug 10, 2026 · wifi: mac80211: free AP_VLAN bc_buf SKBs outside IRQ lock0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2a665946e0407a05a3f81bd56a08553c446498e0 | Vendor (CNA) |
| Linux Linux | 5c342437ea44bb829680ca9e4f683dd5b325b219 | Vendor (CNA) |
| Linux Linux | 6bd21ec8549a5854dd64204a66289952917a924c | Vendor (CNA) |
| Linux Linux | 860887d22890417d43ef8298f0cc4865e29b54de | Vendor (CNA) |
| Linux Linux | 9a4be91e5bb032b34cb3c962f6d4f82e7ef09364 | Vendor (CNA) |
| Linux Linux | c73c3fc1c7ca5a927639f0884624cb244ba791e4 | Vendor (CNA) |
| Linux Linux | f50a2b9e57a751e70ae9a272875d80d39eaccd6a | Vendor (CNA) |
| Linux Linux | fb12c87ae855346321af72e57a93c146205f1090 | Vendor (CNA) |
| azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 | 6.6.150.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0800 · Aug 11, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/5c342437ea44bb829680ca9e4f683dd5b325b219
- git.kernel.org/stable/c/6bd21ec8549a5854dd64204a66289952917a924c
- git.kernel.org/stable/c/860887d22890417d43ef8298f0cc4865e29b54de
- git.kernel.org/stable/c/9a4be91e5bb032b34cb3c962f6d4f82e7ef09364
- git.kernel.org/stable/c/c73c3fc1c7ca5a927639f0884624cb244ba791e4
- git.kernel.org/stable/c/f50a2b9e57a751e70ae9a272875d80d39eaccd6a
- git.kernel.org/stable/c/fb12c87ae855346321af72e57a93c146205f1090
Vendor advisories and official records. Exploit/PoC links are deliberately left out.