net: atl1: fix soft lockup on out-of-range cmb_tpd_next_to_clean read
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f3cc28c797604fa1cda4aef3f250f465de54a0ca · < 0f573b0576252d44fb27ab8470ea873bc6408ef3| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: atl1: fix soft lockup on out-of-range cmb_tpd_next_to_clean read
Same issue as atl1c (see the first commit in this series, "net: atl1c: fix soft lockup on out-of-range tpd_cons read"): the hardware can report an out-of-range cmb_tpd_next_to_clean (seen as 0xffff) while the PCIe link/MAC is resetting. An out-of-range value can never be reached and the loop below would spin forever. Treat it as "nothing new to clean" instead.
From the CVE record · Linux
The Linux kernel’s atl1 driver can spin indefinitely if hardware reports an out-of-range transmit cleanup value while the PCIe link or MAC is resetting. This can cause a soft lockup. The input does not specify an attacker path, authentication requirement, or user interaction.
Engineers running Linux kernels with the atl1 network driver should check whether their kernel includes the fix; affected versions are not specified.