CVE-2026-99475
genirq: Defer kfree(irqaction) until irq_thread_dtor() finishes
What happened?
In the Linux kernel, the following vulnerability has been resolved:
genirq: Defer kfree(irqaction) until irq_thread_dtor() finishes
When an interrupt thread exits abnormally via do_exit() (e.g. the interrupt handler oopses) without returning from irq_thread(), a concurrent call to free_irq() could free the irqaction before the irq_thread_dtor() exit task work runs.
irq thread (oopsed) free_irq() ------------------- ---------- do_exit() exit_mm() complete_vfork_done() -------> kthread_stop() returns exit_files() ... kfree(action) exit_task_work() irq_thread_dtor() action->... <- use-after-free
Track the pending exit work with the IRQTF_EXIT_WORK thread flag, and have __free_irq() wait for the bit to clear before kfree().
irq_thread_dtor() only runs on irq_thread abnormal exit. If that dtor also faults, free_irq() will hang indefinitely, but double IRQ thread faults require a reboot anyways.
[ tglx: Add missing include ]
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: ed3e694d78cc75fa79bf29698631b146fd27aa35 to < ec397edc4c8ca868865953926831b539698469e6; affected: ed3e694d78cc75fa79bf29698631b146fd27aa35 to < a6deaadd460a3a3cfd59c857247097e8da892af8; affected: ed3e694d78cc75fa79bf29698631b146fd27aa35 to < 08aaea3e62b2ddc69a65d52609a5924559d05af2; affected: ed3e694d78cc75fa79bf29698631b146fd27aa35 to < d04adff6860587e843948b0c31174f8ae11b8dfe | See vendor advisory |
| LinuxLinux | affected: 3.6; unaffected: 0 to < 3.6; unaffected: 6.12.117 to ≤ 6.12.*; unaffected: 6.18.61 to ≤ 6.18.*; unaffected: 7.3.2 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-99475
- https://git.kernel.org/stable/c/ec397edc4c8ca868865953926831b539698469e6
- https://git.kernel.org/stable/c/a6deaadd460a3a3cfd59c857247097e8da892af8
- https://git.kernel.org/stable/c/08aaea3e62b2ddc69a65d52609a5924559d05af2
- https://git.kernel.org/stable/c/d04adff6860587e843948b0c31174f8ae11b8dfe