net: cadence: macb: Fix a possible deadlock in macb_halt_tx.
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e86cd53afc5907f7c221b709916e2dd354e14691 · < 84f98955a9de0e0f591df85aa1a44f3ebcf1cb37| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: cadence: macb: Fix a possible deadlock in macb_halt_tx.
There is a situation where after THALT is set high, TGO stays high as well. Because jiffies are never updated, as we are in a context with interrupts disabled, we never exit that loop and have a deadlock.
That deadlock was noticed on a sama5d4 device that stayed locked for days.
Use retries instead of jiffies so that the timeout really works and we do not have a deadlock anymore.
From the CVE record · Linux
The Linux kernel’s cadence macb network driver can deadlock in macb_halt_tx when TGO remains high after THALT is set and interrupts are disabled. The loop’s jiffies-based timeout does not advance in that context, potentially leaving a device locked indefinitely. The input does not describe an attacker trigger, required access, or user interaction.
Engineers running Linux kernels with the cadence macb network driver should check whether their kernel is affected; affected versions are not specified.