https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 13:40:35 +0000 https://vulnerability.circl.lu/vuln/cve-2026-23013 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: octeon_ep_vf: fix free_irq dev_id mismatch in IRQ rollback</p> <p>octep_vf_request_irqs() requests MSI-X queue IRQs with dev_id set to ioq_vector. If request_irq() fails part-way, the rollback loop calls free_irq() with dev_id set to &#39;oct&#39;, which does not match the original dev_id and may leave the irqaction registered.</p> <p>This can keep IRQ handlers alive while ioq_vector is later freed during unwind/teardown, leading to a use-after-free or crash when an interrupt fires.</p> <p>Fix the error path to free IRQs with the same ioq_vector dev_id used during request_irq().</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: octeon_ep_vf: fix free_irq dev_id mismatch in IRQ rollback</p> <p>octep_vf_request_irqs() requests MSI-X queue IRQs with dev_id set to ioq_vector. If request_irq() fails part-way, the rollback loop calls free_irq() with dev_id set to &#39;oct&#39;, which does not match the original dev_id and may leave the irqaction registered.</p> <p>This can keep IRQ handlers alive while ioq_vector is later freed during unwind/teardown, leading to a use-after-free or crash when an interrupt fires.</p> <p>Fix the error path to free IRQs with the same ioq_vector dev_id used during request_irq().</p> https://vulnerability.circl.lu/vuln/cve-2026-23013