net: atl1e: fix soft lockup on out-of-range hw_next_to_clean read
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ a6a5325239c20202e18e21e94291bccc659fbf9e · < 4b7161804d8f31227551901f93947bb4eea4690b| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: atl1e: fix soft lockup on out-of-range hw_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 hw_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 atl1e network driver can enter an endless loop if hardware reports an out-of-range value while the PCIe link or MAC is resetting. This can cause a soft lockup. The input does not describe an attacker path or any authentication or user-interaction requirements.
Operators running Linux kernels with the atl1e driver should check their exposure; affected versions are not specified.