wifi: rt2x00: avoid full teardown before work setup in probe
In the Linux kernel, the following vulnerability has been resolved: wifi: rt2x00: avoid full teardown before work setup in probe rt2x00lib_probe_dev() uses the full rt2x00lib_remove_dev() teardown for all probe failures. However, drv_data allocation and workqueue allocation can fail before intf_work, autowakeup_work and sleep_work have been initialized. Do not enter the full remove path until the probe has reached the point where those work items are set up. Return directly for drv_data allocation failure, and use a small early cleanup path for workqueue allocation failure. This issue was found by our static analysis tool and then confirmed by manual review of rt2x00lib_probe_dev() and rt2x00lib_remove_dev(). The early probe exits should not call a common teardown path that assumes the later work setup has already completed. A QEMU PoC forced alloc_ordered_workqueue() to fail before the work initializers are reached. The resulting fail path entered rt2x00lib_remove_dev(), and DEBUG_OBJECTS reported invalid work drains with rt2x00lib_probe_dev() and rt2x00lib_remove_dev() in the stack.
- Published
- Aug 15, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.2% · 6th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
—
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
- 2.6.39affected
- 0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 and later · before 8b58d1f1356df6a7d2de3f55bb665b18b04ffda0affected · git
- 0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 and later · before 59afe6148927395cf86f9429900e029a48b1d42baffected · git
- 0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 and later · before 3c0427d719bddb33caf18ff4ffb77cb47de7eb00affected · git
- 0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 and later · before eb7474d0253bb2de4793e1d3ce833e8564bbe732affected · git
- 0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 and later · before 66bd9b1a72de7c2f5141b02d796048aafaed8a49affected · git
- 0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 and later · before 816559409e340acaa5c9d868291dab30d8c80263affected · git
- 0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 and later · before 56994852d704535ea354a4627ca667b1b4fa0debaffected · git
- 0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 and later · before 536fb3d739d75a03cb318c0c6fe799425cfea501affected · git
- before 2.6.39not 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.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-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
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
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 | 3c0427d719bddb33caf18ff4ffb77cb47de7eb00 | Vendor (CNA) |
| Linux Linux | 536fb3d739d75a03cb318c0c6fe799425cfea501 | Vendor (CNA) |
| Linux Linux | 56994852d704535ea354a4627ca667b1b4fa0deb | Vendor (CNA) |
| Linux Linux | 59afe6148927395cf86f9429900e029a48b1d42b | Vendor (CNA) |
| Linux Linux | 66bd9b1a72de7c2f5141b02d796048aafaed8a49 | Vendor (CNA) |
| Linux Linux | 816559409e340acaa5c9d868291dab30d8c80263 | Vendor (CNA) |
| Linux Linux | 8b58d1f1356df6a7d2de3f55bb665b18b04ffda0 | Vendor (CNA) |
| Linux Linux | eb7474d0253bb2de4793e1d3ce833e8564bbe732 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · 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).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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
- git.kernel.org/stable/c/3c0427d719bddb33caf18ff4ffb77cb47de7eb00
- git.kernel.org/stable/c/536fb3d739d75a03cb318c0c6fe799425cfea501
- git.kernel.org/stable/c/56994852d704535ea354a4627ca667b1b4fa0deb
- git.kernel.org/stable/c/59afe6148927395cf86f9429900e029a48b1d42b
- git.kernel.org/stable/c/66bd9b1a72de7c2f5141b02d796048aafaed8a49
- git.kernel.org/stable/c/816559409e340acaa5c9d868291dab30d8c80263
- git.kernel.org/stable/c/8b58d1f1356df6a7d2de3f55bb665b18b04ffda0
- git.kernel.org/stable/c/eb7474d0253bb2de4793e1d3ce833e8564bbe732
Vendor advisories and official records. Exploit/PoC links are deliberately left out.