LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50714: wifi: mt76: mt7921e: fix rmmod crash in driver reload test

In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7921e: fix rmmod crash in driver reload test In insmod/rmmod stress test, the following crash dump shows up immediately. The problem is caused by missing mt76_dev in mt7921_pci_remove(). We should make sure the drvdata is ready before probe() finished. [168.862789] ================================================================== [168.862797] BUG: KASAN: user-memory-access in try_to_grab_pending+0x59/0x480 [168.862805] Write of size 8 at addr 0000000000006df0 by task rmmod/5361 [168.862812] CPU: 7 PID: 5361 Comm: rmmod Tainted: G OE 5.19.0-rc6 #1 [168.862816] Hardware name: Intel(R) Client Systems NUC8i7BEH/NUC8BEB, 05/04/2020 [168.862820] Call Trace: [168.862822] <TASK> [168.862825] dump_stack_lvl+0x49/0x63 [168.862832] print_report.cold+0x493/0x6b7 [168.862845] kasan_report+0xa7/0x120 [168.862857] kasan_check_range+0x163/0x200 [168.862861] __kasan_check_write+0x14/0x20 [168.862866] try_to_grab_pending+0x59/0x480 [168.862870] __cancel_work_timer+0xbb/0x340 [168.862898] cancel_work_sync+0x10/0x20 [168.862902] mt7921_pci_remove+0x61/0x1c0 [mt7921e] [168.862909] pci_device_remove+0xa3/0x1d0 [168.862914] device_remove+0xc4/0x170 [168.862920] device_release_driver_internal+0x163/0x300 [168.862925] driver_detach+0xc7/0x1a0 [168.862930] bus_remove_driver+0xeb/0x2d0 [168.862935] driver_unregister+0x71/0xb0 [168.862939] pci_unregister_driver+0x30/0x230 [168.862944] mt7921_pci_driver_exit+0x10/0x1b [mt7921e] [168.862949] __x64_sys_delete_module+0x2f9/0x4b0 [168.862968] do_syscall_64+0x38/0x90 [168.862973] entry_SYSCALL_64_after_hwframe+0x63/0xcd Test steps: 1. insmode 2. do not ifup 3. rmmod quickly (within 1 second)

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel driver reliability flaw in the MediaTek mt7921e Wi-Fi driver. Under a rapid driver reload stress condition, the kernel can crash. Evidence points to local, privileged conditions rather than remote exploitation. There is no CISA KEV listing or cited evidence of active exploitation.

Executive priority

Treat as routine patch management unless affected laptops or appliances frequently reload Wi-Fi drivers. The risk is mainly local system crash, not confirmed remote compromise. Prioritize through normal kernel update cycles for exposed fleets.

Technical view

CVE-2022-50714 fixes a crash in mt76/mt7921e during module removal when driver data is not ready before probe completion. The reported crash occurs in mt7921_pci_remove() during work cancellation. Linux stable commits are referenced as fixes; CVSS and CWE details are not provided in the source bundle.

Likely exposure

Exposure is likely limited to Linux systems using the mt7921e PCIe Wi-Fi driver, especially kernels in affected ranges before stable fixes. Practical triggering appears to require local ability to load or unload kernel modules, typically privileged access.

Exploitation context

The public description ties the issue to an insmod/rmmod driver reload stress test. No source in the bundle claims remote exploitation, privilege escalation, public weaponization, or active exploitation. Business impact is most likely local denial of service through a kernel crash.

Researcher notes

The source bundle lacks CVSS, CWE, and detailed affected range formatting. It references three Linux stable commits and describes a KASAN user-memory-access crash during mt7921e removal. Avoid assuming exploitability beyond the documented local crash condition.

Mitigation direction

  • Update to a kernel containing the referenced Linux stable fixes.
  • Check your Linux distribution advisory for the backported fixed package.
  • Prioritize systems with MediaTek MT7921e Wi-Fi hardware and module reload workflows.
  • Restrict kernel module load and unload permissions to trusted administrators.

Validation and detection

  • Inventory systems using the mt7921e or mt76 Linux Wi-Fi drivers.
  • Compare running kernel versions against distro-fixed packages or referenced stable commits.
  • Review kernel logs for mt7921_pci_remove or rmmod crash signatures.
  • Confirm patched systems no longer carry the affected driver code path.
Prepared
Confidence
medium
Sources
5

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-50714 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1c71e03afe4b457a15e50de40006b927dfc00755, 1c71e03afe4b457a15e50de40006b927dfc00755, 1c71e03afe4b457a15e50de40006b927dfc00755unaffected
LinuxLinux5.18, 0, 5.19.17, 6.0.3, 6.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.