In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7996: hold dev->mt76.mutex while disabling tx worker in SER… (CVE-2026-90367)
A high-severity vulnerability in the Linux kernel's mt76 wifi driver (specifically mt7996) involves improper mutex handling during the disabling of the TX worker in a channel reset scenario. This flaw can lead to corruption of DMA descriptors or tokens due to race conditions between error recovery and channel switching.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel's mt76 wifi driver (mt7996) arises because mt7996_mac_reset_work() disables the TX worker and RX/TX NAPIs before acquiring the dev->mt76.mutex. Since mt76_worker_disable() and _enable() are simple thread park/unpark operations without reference counting, a race condition can occur during an L1 SER (single event recovery) and channel switch. This race can cause the TX worker to be unparked and the MT76_RESET bit cleared while the reset path resets DMA rings, potentially corrupting descriptors or tokens. The fix involves acquiring the mutex before disabling the worker, aligning with the approach used in the mt7915 driver.
Potential Impact
If exploited, this race condition can cause corruption of DMA descriptors or tokens in the wifi driver, potentially leading to denial of service or other unpredictable behavior affecting wifi functionality. The CVSS score of 8.8 indicates a high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
The vulnerability has been resolved in the Linux kernel by ensuring the dev->mt76.mutex is held while disabling the TX worker during reset operations. Users should apply the official Linux kernel updates that include this fix. No additional mitigation steps are indicated.
In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7996: hold dev->mt76.mutex while disabling tx worker in SER… (CVE-2026-90367)
Description
A high-severity vulnerability in the Linux kernel's mt76 wifi driver (specifically mt7996) involves improper mutex handling during the disabling of the TX worker in a channel reset scenario. This flaw can lead to corruption of DMA descriptors or tokens due to race conditions between error recovery and channel switching.
CVSS v3.1
Score 8.8high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel's mt76 wifi driver (mt7996) arises because mt7996_mac_reset_work() disables the TX worker and RX/TX NAPIs before acquiring the dev->mt76.mutex. Since mt76_worker_disable() and _enable() are simple thread park/unpark operations without reference counting, a race condition can occur during an L1 SER (single event recovery) and channel switch. This race can cause the TX worker to be unparked and the MT76_RESET bit cleared while the reset path resets DMA rings, potentially corrupting descriptors or tokens. The fix involves acquiring the mutex before disabling the worker, aligning with the approach used in the mt7915 driver.
Potential Impact
If exploited, this race condition can cause corruption of DMA descriptors or tokens in the wifi driver, potentially leading to denial of service or other unpredictable behavior affecting wifi functionality. The CVSS score of 8.8 indicates a high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
The vulnerability has been resolved in the Linux kernel by ensuring the dev->mt76.mutex is held while disabling the TX worker during reset operations. Users should apply the official Linux kernel updates that include this fix. No additional mitigation steps are indicated.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-rjqr-mg4v-422g
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-90367"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6aade51d55bf5e2cf5edc0b1
Added to database: 09/19/2026, 01:27:57 UTC
Last enriched: 09/19/2026, 01:47:10 UTC
Last updated: 09/19/2026, 04:21:38 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.