ice: fix NULL access of tx->in_use in ice_ll_ts_intr
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.466.16.66.17In the Linux kernel, the following vulnerability has been resolved:
ice: fix NULL access of tx->in_use in ice_ll_ts_intr
Recent versions of the E810 firmware have support for an extra interrupt to handle report of the "low latency" Tx timestamps coming from the specialized low latency firmware interface. Instead of polling the registers, software can wait until the low latency interrupt is fired.
This logic makes use of the Tx timestamp tracking structure, ice_ptp_tx, as it uses the same "ready" bitmap to track which Tx timestamps complete.
Unfortunately, the ice_ll_ts_intr() function does not check if the tracker is initialized before its first access. This results in NULL dereference or use-after-free bugs similar to the issues fixed in the ice_ptp_ts_irq() function.
Fix this by only checking the in_use bitmap (and other fields) if the tracker is marked as initialized. The reset flow will clear the init field under lock before it tears the tracker down, thus preventing any use-after-free or NULL access.
From the CVE record · Linux
The Linux kernel’s ice low-latency Tx timestamp interrupt handler can access a timestamp tracker before it is initialized or after it is torn down, causing a NULL dereference or use-after-free. This can occur when handling the extra interrupt supported by recent E810 firmware; the input does not specify attacker access requirements or user interaction.
Engineers running Linux kernels with the ice driver and E810 firmware that supports the low-latency Tx timestamp interrupt should check whether their kernel includes the fix; affected versions are not specified.