CVE-2024-26892: wifi: mt76: mt7921e: fix use-after-free in free_irq()
In the Linux kernel, the following vulnerability has been resolved:
wifi: mt76: mt7921e: fix use-after-free in free_irq()
From commit a304e1b82808 ("[PATCH] Debug shared irqs"), there is a test
to make sure the shared irq handler should be able to handle the unexpected
event after deregistration. For this case, let's apply MT76_REMOVED flag to
indicate the device was removed and do not run into the resource access
anymore.
BUG: KASAN: use-after-free in mt7921_irq_handler+0xd8/0x100 [mt7921e]
Read of size 8 at addr ffff88824a7d3b78 by task rmmod/11115
CPU: 28 PID: 11115 Comm: rmmod Tainted: G W L 5.17.0 #10
Hardware name: Micro-Star International Co., Ltd. MS-7D73/MPG B650I
EDGE WIFI (MS-7D73), BIOS 1.81 01/05/2024
Call Trace:
<TASK>
dump_stack_lvl+0x6f/0xa0
print_address_description.constprop.0+0x1f/0x190
? mt7921_irq_handler+0xd8/0x100 [mt7921e]
? mt7921_irq_handler+0xd8/0x100 [mt7921e]
kasan_report.cold+0x7f/0x11b
? mt7921_irq_handler+0xd8/0x100 [mt7921e]
mt7921_irq_handler+0xd8/0x100 [mt7921e]
free_irq+0x627/0xaa0
devm_free_irq+0x94/0xd0
? devm_request_any_context_irq+0x160/0x160
? kobject_put+0x18d/0x4a0
mt7921_pci_remove+0x153/0x190 [mt7921e]
pci_device_remove+0xa2/0x1d0
__device_release_driver+0x346/0x6e0
driver_detach+0x1ef/0x2c0
bus_remove_driver+0xe7/0x2d0
? __check_object_size+0x57/0x310
pci_unregister_driver+0x26/0x250
__do_sys_delete_module+0x307/0x510
? free_module+0x6a0/0x6a0
? fpregs_assert_state_consistent+0x4b/0xb0
? rcu_read_lock_sched_held+0x10/0x70
? syscall_enter_from_user_mode+0x20/0x70
? trace_hardirqs_on+0x1c/0x130
do_syscall_64+0x5c/0x80
? trace_hardirqs_on_prepare+0x72/0x160
? do_syscall_64+0x68/0x80
? trace_hardirqs_on_prepare+0x72/0x160
entry_SYSCALL_64_after_hwframe+0x44/0xae
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel driver bug in the MediaTek MT7921E Wi-Fi PCIe driver. During device or module removal, the interrupt handler could access already-freed memory. The business risk is most relevant to Linux laptops, workstations, or appliances using that Wi-Fi chipset, where the issue could cause instability or undefined kernel behavior.
Executive priority
Treat as a targeted kernel maintenance item for Linux endpoint fleets using MediaTek Wi-Fi. It does not warrant emergency response without matching hardware, affected kernels, or operational instability evidence.
Technical view
The mt76 mt7921e driver had a use-after-free path in free_irq() after IRQ deregistration. The fix marks the device removed with MT76_REMOVED so the shared IRQ handler stops accessing resources after teardown. The source bundle includes KASAN evidence during rmmod and stable kernel fix commits.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions with the mt7921e driver and compatible MediaTek MT7921E PCIe Wi-Fi hardware. Cloud servers and systems without this driver or hardware are less likely exposed.
Exploitation context
The provided sources do not show active exploitation, public exploit code, or CISA KEV listing. The observed trigger is module or device removal involving shared IRQ cleanup, not a documented remote attack path.
Researcher notes
Evidence is strong for the bug class and fix path, but incomplete for impact severity. No CVSS, CWE, exploitability analysis, or distribution-specific fixed package data is included in the provided bundle.
Mitigation direction
Identify Linux systems using the mt7921e driver and MT7921E Wi-Fi hardware.
Prioritize kernel updates containing the referenced stable fixes.
Check distribution vendor advisories for backported kernel packages.
Avoid unnecessary driver unload or device removal on exposed systems until patched.
Validation and detection
Inventory loaded kernel modules for mt7921e on Linux endpoints.
Map running kernel versions against vendor fixed kernel builds.
Confirm installed kernel includes one of the referenced stable commits or vendor backport.
Review kernel logs for KASAN or crash reports involving mt7921_irq_handler.
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-2024-26892 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.