Kernel crash via unrequested IRQ release
Published May 21, 2024 · Updated May 11, 2026
Denial of service in Linux kernel mISDN netjet code allows local users to crash the system when a NetJet device probe fails. The nj_setup failure path leaves card->irq positive before request_irq runs, so nj_release calls free_irq for an IRQ that was never requested. Reaching the fault requires the mISDN netjet driver and a failing NetJet PCI probe; with panic_on_warn enabled, the warning becomes a kernel panic.
Summary
What happened
Denial of service in Linux kernel mISDN netjet code allows local users to crash the system when a NetJet device probe fails. The nj_setup failure path leaves card->irq positive before request_irq runs, so nj_release calls free_irq for an IRQ that was never requested. Reaching the fault requires the mISDN netjet driver and a failing NetJet PCI probe; with panic_on_warn enabled, the warning becomes a kernel panic.
The record
- CVE
- CVE-2021-47284
- Published
- May 21, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-400, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 21, 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=2.6.32
- Affected versionversion=a900845e56617edc005fd8f35bfd5a407aaf96c8 <143fc7220961220eecc04669e5909af8847bf8c8
- Affected versionversion=a900845e56617edc005fd8f35bfd5a407aaf96c8 <4c1fcb6ec964b44edbf84235134582a5ffae1521
- Affected versionversion=a900845e56617edc005fd8f35bfd5a407aaf96c8 <6249193e03709ea625e10706ecaf17fea0427d3d
- Affected versionversion=a900845e56617edc005fd8f35bfd5a407aaf96c8 <958cb1078ca60d214826fd90a0961a447fade59a
- Affected versionversion=a900845e56617edc005fd8f35bfd5a407aaf96c8 <9d7d4649dc1c53acf76df260fd519db698ed20d7
- Affected versionversion=a900845e56617edc005fd8f35bfd5a407aaf96c8 <9f6f852550d0e1b7735651228116ae9d300f69b3
- Affected versionversion=a900845e56617edc005fd8f35bfd5a407aaf96c8 <a0a37e4454ca1c0b424edc2c9c2487c2c46a1be6
- Affected versionversion=a900845e56617edc005fd8f35bfd5a407aaf96c8 <bf78e25bd3f487208e042c67c8a31706c2dba265
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.
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