CVE-2026-90373: wifi: mt76: mt7915: clear wcid mask under mutex after RCU pointer clear
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.20% (FIRST EPSS).
- Fixed version: Linux Linux 5dce25f1d609ba991a9c22c27be586c92f03ed77, 6.2, 6.7.
Low priority for now. Upgrade to Linux Linux 5dce25f1d609ba991a9c22c27be586c92f03ed77, 6.2, 6.7 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: mt76: mt7915: clear wcid mask under mutex after RCU pointer clear mt7915_remove_interface() cleared the wcid mask bit with no lock held and before clearing the RCU wcid pointer. The mask is a non-atomic RMW shared with the allocators, which all run under dev->mt76.mutex; on DBDC the two wiphys share one mt76_dev, so this raced add_interface/sta_add on the other band and could leak or double-hand-out a wcid. Clearing the bit before the RCU pointer also let a concurrent allocation reuse the index and publish its wcid, which the subsequent NULL assignment then wiped. Move the clear into the existing mutex section, after the RCU pointer is cleared.
- Published
- Sep 17, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
Is your version affected? Check itNoroxi 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
- b7c8e22dfddacc1b08dbf44f5be2c66305d757bc, a582b1d54313dcdc96e7d8e1f49495dd71ddaf3e, 6.12affected
- f3049b88b2b32326df97461813ae73e8bbc296fc and later · before 5dce25f1d609ba991a9c22c27be586c92f03ed77affected · git
- f3049b88b2b32326df97461813ae73e8bbc296fc and later · before b4a41a47a67c788e6b0625fa517ec8872e99bb6caffected · git
- f3049b88b2b32326df97461813ae73e8bbc296fc and later · before a97b2b942d2f8f12fbd6a7caafc735d1ad115e6baffected · git
- f3049b88b2b32326df97461813ae73e8bbc296fc and later · before 6486e11a6e2f679597af2d5bb48c3b07a2b2a7baaffected · git
- 6.1.191 and later · before 6.2affected · semver
- 6.6.160 and later · before 6.7affected · semver
- before 6.12not affected · semver
- 6.12.110 and later · up to and including 6.12.*not affected · semver
- 6.18.52 and later · up to and including 6.18.*not 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-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.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-90371Sep 17, 2026 · wifi: mt76: fix RXDMAD_C buffer recycling race35Monitor
- ← EarlierCVE-2026-90372Sep 17, 2026 · wifi: mt76: mt7915: avoid nss underflow in mt7915_mcu_get_sta_nss28Monitor
- Later →CVE-2026-90374Sep 17, 2026 · wifi: mt76: mt7996: validate RX band_idx before dereferencing phys[]0Monitor
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 | 5dce25f1d609ba991a9c22c27be586c92f03ed77 | Vendor (CNA) |
| Linux Linux | 6.2 | Vendor (CNA) |
| Linux Linux | 6.7 | Vendor (CNA) |
| Linux Linux | 6486e11a6e2f679597af2d5bb48c3b07a2b2a7ba | Vendor (CNA) |
| Linux Linux | a97b2b942d2f8f12fbd6a7caafc735d1ad115e6b | Vendor (CNA) |
| Linux Linux | b4a41a47a67c788e6b0625fa517ec8872e99bb6c | Vendor (CNA) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-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).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.