net: octeon_ep_vf: fix free_irq dev_id mismatch in IRQ rollback
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.12.676.18.76.19In the Linux kernel, the following vulnerability has been resolved:
net: octeon_ep_vf: fix free_irq dev_id mismatch in IRQ rollback
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 'oct', which does not match the original dev_id and may leave the irqaction registered.
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.
Fix the error path to free IRQs with the same ioq_vector dev_id used during request_irq().
From the CVE record · Linux
The Linux kernel’s octeon_ep_vf driver can leave an IRQ handler registered if MSI-X queue IRQ setup fails part-way through, because the rollback uses the wrong dev_id. If an interrupt fires after the associated ioq_vector is freed, this can cause a use-after-free or crash. The input does not establish whether an attacker can trigger these conditions or whether authentication or user interaction is required.
Engineers running Linux kernels with the octeon_ep_vf driver should check their kernel versions against the vendor advisory; affected versions were not provided.