PCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0)
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 18b0415bc802a8bab5dedba5ae2757e83259e6ee · < dd47051c76c8acd8cb983f01b4d1265da29cb66a| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
PCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0)
Errata #i2037 in AM65x/DRA80xM Processors Silicon Revision 1.0 (SPRZ452D_July 2018_Revised December 2019 [1]) mentions when an inbound PCIe TLP spans more than two internal AXI 128-byte bursts, the bus may corrupt the packet payload and the corrupt data may cause associated applications or the processor to hang.
The workaround for Errata #i2037 is to limit the maximum read request size and maximum payload size to 128 bytes. Add workaround for Errata #i2037 here.
The errata and workaround is applicable only to AM65x SR 1.0 and later versions of the silicon will have this fixed.
[1] -> https://www.ti.com/lit/er/sprz452i/sprz452i.pdf
From the CVE record · Linux
On AM65x silicon revision 1.0, an inbound PCIe transaction spanning more than two internal 128-byte AXI bursts can corrupt data and cause applications or the processor to hang. Someone able to induce such a transaction could trigger a hang; the input does not specify network access, authentication requirements, or user interaction.
Engineers running Linux on AM65x silicon revision 1.0 should check their kernel; affected kernel versions are not specified.