Kernel crash via post-deregistration interrupt handling
Published Apr 17, 2024 · Updated May 23, 2026
Use-after-free in the mt7921e Wi-Fi driver in Linux allows local users to crash the kernel during PCI device removal. During mt7921_pci_remove, free_irq can invoke the shared mt7921_irq_handler after deregistration, and the handler reads freed device resources because removal state is not marked. Reaching the flaw requires administrative ability to remove the PCI driver while an unexpected shared interrupt is handled; the demonstrated consequence is a KASAN-detected kernel memory access that can crash the system.
Summary
What happened
Use-after-free in the mt7921e Wi-Fi driver in Linux allows local users to crash the kernel during PCI device removal. During mt7921_pci_remove, free_irq can invoke the shared mt7921_irq_handler after deregistration, and the handler reads freed device resources because removal state is not marked. Reaching the flaw requires administrative ability to remove the PCI driver while an unexpected shared interrupt is handled; the demonstrated consequence is a KASAN-detected kernel memory access that can crash the system.
The record
- CVE
- CVE-2024-26892
- Published
- Apr 17, 2024
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Apr 17, 2024CVE publishedPublication date reported by the CVE source.
- May 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.2.15 <6.3
- Affected versionversion=6.3.2 <6.4
- Affected versionversion=6.4
- Affected versionversion=9270270d62191b7549296721e8d5f3dc0df01563 <bfe1adf1606f76c180324e53b130f0e76d5cc6c3
- Affected versionversion=9270270d62191b7549296721e8d5f3dc0df01563 <bfeaef901194c5923ce3330272786eff2fac513a
- Affected versionversion=9270270d62191b7549296721e8d5f3dc0df01563 <c7dd42fbebcfb02bef070fd48f774d6412d0b49d
- Affected versionversion=9270270d62191b7549296721e8d5f3dc0df01563 <c957280ef6ab6bdf559a91ae693a6b34310697e3
- Affected versionversion=95e41ac30a0d0b3637f0b3c93235a7a107a2fb7f
- Affected versionversion=a76eaaaafd8b408238d7865bbbbd311f08988f3d
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo