CVE-2022-48705: wifi: mt76: mt7921e: fix crash in chip reset fail
In the Linux kernel, the following vulnerability has been resolved:
wifi: mt76: mt7921e: fix crash in chip reset fail
In case of drv own fail in reset, we may need to run mac_reset several
times. The sequence would trigger system crash as the log below.
Because we do not re-enable/schedule "tx_napi" before disable it again,
the process would keep waiting for state change in napi_diable(). To
avoid the problem and keep status synchronize for each run, goto final
resource handling if drv own failed.
[ 5857.353423] mt7921e 0000:3b:00.0: driver own failed
[ 5858.433427] mt7921e 0000:3b:00.0: Timeout for driver own
[ 5859.633430] mt7921e 0000:3b:00.0: driver own failed
[ 5859.633444] ------------[ cut here ]------------
[ 5859.633446] WARNING: CPU: 6 at kernel/kthread.c:659 kthread_park+0x11d
[ 5859.633717] Workqueue: mt76 mt7921_mac_reset_work [mt7921_common]
[ 5859.633728] RIP: 0010:kthread_park+0x11d/0x150
[ 5859.633736] RSP: 0018:ffff8881b676fc68 EFLAGS: 00010202
......
[ 5859.633766] Call Trace:
[ 5859.633768] <TASK>
[ 5859.633771] mt7921e_mac_reset+0x176/0x6f0 [mt7921e]
[ 5859.633778] mt7921_mac_reset_work+0x184/0x3a0 [mt7921_common]
[ 5859.633785] ? mt7921_mac_set_timing+0x520/0x520 [mt7921_common]
[ 5859.633794] ? __kasan_check_read+0x11/0x20
[ 5859.633802] process_one_work+0x7ee/0x1320
[ 5859.633810] worker_thread+0x53c/0x1240
[ 5859.633818] kthread+0x2b8/0x370
[ 5859.633824] ? process_one_work+0x1320/0x1320
[ 5859.633828] ? kthread_complete_and_exit+0x30/0x30
[ 5859.633834] ret_from_fork+0x1f/0x30
[ 5859.633842] </TASK>
Security readout for executives and security teams
Plain-English summary
This CVE is a Linux kernel Wi-Fi driver crash involving the MediaTek mt7921e driver. During a failed chip reset, repeated reset handling can leave NAPI state unsynchronized and crash the system. Business impact is mainly availability on systems using this hardware and affected kernels.
Executive priority
Handle through normal kernel patch management, with higher priority for fleets using MT7921e Wi-Fi. This is an availability risk, not proven active exploitation in the supplied evidence.
Technical view
The mt76 mt7921e reset path can call reset handling again after “driver own” failure without re-enabling or scheduling tx_napi before disabling it again. That can block in napi_disable/kthread handling and trigger a kernel warning/crash. Stable kernel commits changed reset failure handling to jump to final resource handling.
Likely exposure
Exposure appears limited to Linux systems with MediaTek MT7921e Wi-Fi hardware using affected kernel versions. The supplied data lists Linux kernel versions including 5.17, 5.19.9, and 6.0 as affected, but version boundaries are not fully described.
Exploitation context
The bundle does not show active exploitation, KEV listing, CVSS, CWE, or a remote attack path. The described trigger is a driver reset failure condition that can cause a local system crash. Treat exploitability details as incomplete.
Researcher notes
The public description is a resolved Linux kernel bug report with crash trace and stable commit references. Evidence supports a reset-path denial-of-service condition, but not attacker prerequisites, remote reachability, CVSS scoring, or complete affected-version boundaries.
Mitigation direction
Identify systems using the mt7921e Wi-Fi driver.
Check vendor kernel advisories for fixed stable releases.
Prioritize kernel updates on laptops or endpoints using MT7921e hardware.
Use the referenced stable commits to confirm downstream backports.
Monitor kernel logs for repeated mt7921e reset failures.
Validation and detection
Inventory loaded Wi-Fi drivers and MediaTek MT7921e hardware.
Compare running kernel versions against vendor fixed builds.
Check kernel package changelogs for the referenced mt76 fix.
Review logs for “driver own failed” or reset crash patterns.
Confirm patched kernels include the stable commit changes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-48705 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.