ieee802154: cc2520: fix FIFOP work use-after-free
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ieee802154: cc2520: fix FIFOP work use-after-free
The FIFOP interrupt handler queues cc2520_fifop_irqwork. On removal, cc2520_remove() only flushes the work. The devm-managed FIFOP IRQ remains active until after ->remove() returns and can queue the work again after that flush, allowing it to run after the private data is released.
Disable the work with disable_work_sync() instead of flushing it, so the handler can no longer queue it once removal begins. Destroy the buffer mutex last, since the worker and the stop callback invoked through ieee802154_unregister_hw() both take it.
Found by an in-house static analysis tool.
From the CVE record · Linux
The Linux kernel's cc2520 IEEE 802.15.4 driver can run queued FIFOP work after its private data is freed. This can occur during device removal if a FIFOP interrupt queues work after the removal callback flushes it. The input does not establish whether an attacker can trigger this condition or what access would be required.
Engineers running Linux kernels with the cc2520 IEEE 802.15.4 driver should check their kernel version against the vendor advisory; affected versions are not specified.