https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 01 Oct 2026 20:16:31 +0000 https://vulnerability.circl.lu/vuln/cve-2026-89769 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>clocksource/drivers/nxp-pit: Fix IRQ leak on cpuhp_setup_state error path</p> <p>When cpuhp_setup_state fails after pit_clockevent_per_cpu_init has successfully called request_irq, the error handling jumps directly to out_pit_clocksource_unregister without freeing the registered IRQ.</p> <p>This leaks the IRQ line and, since kfree(pit) follows, leaves a dangling pointer registered as the interrupt handler&#39;s dev_id, potentially leading to a use-after-free if the IRQ fires afterwards.</p> <p>Fix it by calling pit_clockevent_per_cpu_exit to properly release the IRQ before falling through to the existing cleanup chain.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>clocksource/drivers/nxp-pit: Fix IRQ leak on cpuhp_setup_state error path</p> <p>When cpuhp_setup_state fails after pit_clockevent_per_cpu_init has successfully called request_irq, the error handling jumps directly to out_pit_clocksource_unregister without freeing the registered IRQ.</p> <p>This leaks the IRQ line and, since kfree(pit) follows, leaves a dangling pointer registered as the interrupt handler&#39;s dev_id, potentially leading to a use-after-free if the IRQ fires afterwards.</p> <p>Fix it by calling pit_clockevent_per_cpu_exit to properly release the IRQ before falling through to the existing cleanup chain.</p> https://vulnerability.circl.lu/vuln/cve-2026-89769