CVE-2026-99475
NVD
Vulnerability Summary
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 ]
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 & Patched Versions
- Linux >= ed3e694d78cc75fa79bf29698631b146fd27aa35 and < ec397edc4c8ca868865953926831b539698469e6
- Linux >= ed3e694d78cc75fa79bf29698631b146fd27aa35 and < a6deaadd460a3a3cfd59c857247097e8da892af8
- Linux >= ed3e694d78cc75fa79bf29698631b146fd27aa35 and < 08aaea3e62b2ddc69a65d52609a5924559d05af2
- Linux >= ed3e694d78cc75fa79bf29698631b146fd27aa35 and < d04adff6860587e843948b0c31174f8ae11b8dfe
- Linux 3.6
- Linux ec397edc4c8ca868865953926831b539698469e6
- Linux a6deaadd460a3a3cfd59c857247097e8da892af8
- Linux 08aaea3e62b2ddc69a65d52609a5924559d05af2
- Linux d04adff6860587e843948b0c31174f8ae11b8dfe
What to do
Fix it during your normal patch cycle. No exploitation is confirmed yet.
- Check whether you run the affected product and which version.
- Update to a patched version listed above, then confirm the new version.
Timeline
- Nov 19, 2026Published
- Nov 19, 2026Record last modified
Score, severity and exploitation changes are tracked from the day Watchtower started logging them.
Get alerts for CVEs like this oneYou are reading CVE-2026-99475. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsExternal References
- Referencehttps://git.kernel.org/stable/c/08aaea3e62b2ddc69a65d52609a5924559d05af2
- Referencehttps://git.kernel.org/stable/c/a6deaadd460a3a3cfd59c857247097e8da892af8
- Referencehttps://git.kernel.org/stable/c/d04adff6860587e843948b0c31174f8ae11b8dfe
- Referencehttps://git.kernel.org/stable/c/ec397edc4c8ca868865953926831b539698469e6
Data last checked: Nov 22, 2026 14:11 UTC