{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50714 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50714 is a vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-50714 and fix it if it is affected.\n\nWhat it is: CVE-2022-50714 is a vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-50714 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-50714/ (Markdown: https://insights.sbomify.com/CVE-2022-50714/index.md)","id":"CVE-2022-50714","markdown":"https://insights.sbomify.com/CVE-2022-50714/index.md","name":"CVE-2022-50714","record":{"aliases":["DEBIAN-CVE-2022-50714","GHSA-265p-gc7h-x375","UBUNTU-CVE-2022-50714"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"high_privilege","summary":"A local attacker with root privileges can cause a kernel crash by rapidly unloading the mt7921e WiFi driver before initialization completes.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mt76: mt7921e: fix rmmod crash in driver reload test\n\nIn insmod/rmmod stress test, the following crash dump shows up immediately.\nThe problem is caused by missing mt76_dev in mt7921_pci_remove(). We\nshould make sure the drvdata is ready before probe() finished.\n\n[168.862789] ==================================================================\n[168.862797] BUG: KASAN: user-memory-access in try_to_grab_pending+0x59/0x480\n[168.862805] Write of size 8 at addr 0000000000006df0 by task rmmod/5361\n[168.862812] CPU: 7 PID: 5361 Comm: rmmod Tainted: G           OE     5.19.0-rc6 #1\n[168.862816] Hardware name: Intel(R) Client Systems NUC8i7BEH/NUC8BEB, 05/04/2020\n[168.862820] Call Trace:\n[168.862822]  \u003cTASK\u003e\n[168.862825]  dump_stack_lvl+0x49/0x63\n[168.862832]  print_report.cold+0x493/0x6b7\n[168.862845]  kasan_report+0xa7/0x120\n[168.862857]  kasan_check_range+0x163/0x200\n[168.862861]  __kasan_check_write+0x14/0x20\n[168.862866]  try_to_grab_pending+0x59/0x480\n[168.862870]  __cancel_work_timer+0xbb/0x340\n[168.862898]  cancel_work_sync+0x10/0x20\n[168.862902]  mt7921_pci_remove+0x61/0x1c0 [mt7921e]\n[168.862909]  pci_device_remove+0xa3/0x1d0\n[168.862914]  device_remove+0xc4/0x170\n[168.862920]  device_release_driver_internal+0x163/0x300\n[168.862925]  driver_detach+0xc7/0x1a0\n[168.862930]  bus_remove_driver+0xeb/0x2d0\n[168.862935]  driver_unregister+0x71/0xb0\n[168.862939]  pci_unregister_driver+0x30/0x230\n[168.862944]  mt7921_pci_driver_exit+0x10/0x1b [mt7921e]\n[168.862949]  __x64_sys_delete_module+0x2f9/0x4b0\n[168.862968]  do_syscall_64+0x38/0x90\n[168.862973]  entry_SYSCALL_64_after_hwframe+0x63/0xcd\n\nTest steps:\n1. insmode\n2. do not ifup\n3. rmmod quickly (within 1 second)","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"wifi: mt76: mt7921e: fix rmmod crash in driver reload test","id":"CVE-2022-50714","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"md/raid1: stop mdx_raid1 thread when raid1 array run failed","id":"CVE-2022-50715"},"packages":[],"prev":{"headline":"clk: visconti: Fix memory leak in visconti_register_pll()","id":"CVE-2022-50713"},"products":["Linux"],"published":"2025-12-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A local attacker with root privileges can cause a kernel crash by rapidly unloading the mt7921e WiFi driver before initialization completes.","url":"https://insights.sbomify.com/CVE-2022-50714/"}