FKIE_CVE-2022-50714

Vulnerability from fkie_nvd - Published: 2025-12-24 13:15 - Updated: 2025-12-24 13:15
Severity ?
Summary
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)
Impacted products
Vendor Product Version

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "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)"
    }
  ],
  "id": "CVE-2022-50714",
  "lastModified": "2025-12-24T13:15:58.030",
  "metrics": {},
  "published": "2025-12-24T13:15:58.030",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/1034d8e08508830161377f136a060e78fc24f2a5"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/b5a62d612b7baf6e09884e4de94decb6391d6a9d"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/ccda3ebdae719d348f90563b6719fba4929ae283"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Received"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…