wifi: mt76: mt7915: fix use-after-free bugs in mt7915_mac_dump_work()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4dbcb9125cc3e10a6d879c10e4f5816d05a87c49 · < 1146d0946b5358fad24812bd39d68f31cd40cc34| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
wifi: mt76: mt7915: fix use-after-free bugs in mt7915_mac_dump_work()
When the mt7915 pci chip is detaching, the mt7915_crash_data is released in mt7915_coredump_unregister(). However, the work item dump_work may still be running or pending, leading to UAF bugs when the already freed crash_data is dereferenced again in mt7915_mac_dump_work().
The race condition can occur as follows:
CPU 0 (removal path) | CPU 1 (workqueue) mt7915_pci_remove() | mt7915_sys_recovery_set() mt7915_unregister_device() | mt7915_reset() mt7915_coredump_unregister() | queue_work() vfree(dev->coredump.crash_data) | mt7915_mac_dump_work() | crash_data-> // UAF
Fix this by ensuring dump_work is properly canceled before the crash_data is deallocated. Add cancel_work_sync() in mt7915_unregister_device() to synchronize with any pending or executing dump work.
From the CVE record · Linux
The Linux kernel’s mt7915 Wi-Fi driver can dereference freed crash data if dump work runs while the PCI device is detaching. This race can cause a use-after-free; the input does not establish whether an attacker can trigger it or whether access or user interaction is required.
Teams running Linux kernels with the mt7915 Wi-Fi driver should check their kernels; affected versions are not specified.