Kernel panic via unreleased IRQ before vector cleanup
Published Feb 28, 2024 · Updated May 11, 2026
Improper cleanup in Linux 5.12 through 5.12.3 allows local users to trigger a kernel panic when MT7921 firmware loading fails. The mt7921_pci_probe error path freed the device after mt7921_register_device failed but left its managed IRQ registered before releasing PCI IRQ vectors. Systems require an MT7921 PCIe adapter and missing or failed firmware; the resulting free_msi_irqs BUG stops the host.
Summary
What happened
Improper cleanup in Linux 5.12 through 5.12.3 allows local users to trigger a kernel panic when MT7921 firmware loading fails. The mt7921_pci_probe error path freed the device after mt7921_register_device failed but left its managed IRQ registered before releasing PCI IRQ vectors. Systems require an MT7921 PCIe adapter and missing or failed firmware; the resulting free_msi_irqs BUG stops the host.
The record
- CVE
- CVE-2021-47027
- Published
- Feb 28, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 28, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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=5.12
- Affected versionversion=5c14a5f944b91371961548b1907802f74a4d2e5c <a46b536cd60c0dbd4bf767c62a8774dec52bf099
- Affected versionversion=5c14a5f944b91371961548b1907802f74a4d2e5c <e230f0c44f011f3270680a506b19b7e84c5e8923
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