wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 99074fc1e67b374b5c72406a23ac01fed806d634 · < 0969c9688389f2e0f65b1a924b0dd6625a3bb776| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path
mwifiex_pcie_request_irq() registers each MSI-X vector with a per-index dev_id (&card->msix_ctx[i]). On a request_irq() failure the cleanup loop "for (j = 0; j < i; j++)" frees msix_entries[j].vector but passes the failed index's &card->msix_ctx[i] as the dev_id. free_irq() matches on (irq, dev_id), so it fails to find the action registered with &card->msix_ctx[j]: the already-requested IRQ j is not freed (leaked) and free_irq() warns about freeing a non-existent IRQ. Use &card->msix_ctx[j].
From the CVE record · Linux
The Linux kernel's mwifiex PCIe driver uses the wrong device ID when cleaning up after an MSI-X IRQ request fails. Previously registered IRQs can remain allocated, and free_irq() can warn. The input does not describe an attacker-controlled trigger or specify authentication or user-interaction requirements.
Engineers running the Linux kernel with the mwifiex PCIe driver should check their installations; affected versions are not specified.