dmaengine: tegra: Fix burst size calculation
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ee17028009d49fffed8cc963455d33b1fd3f1d08 · < 4651df83b6c796daead3447e8fd874322918ee4f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
dmaengine: tegra: Fix burst size calculation
Currently, the Tegra GPC DMA hardware requires the transfer length to be a multiple of the max burst size configured for the channel. When a client requests a transfer where the length is not evenly divisible by the configured max burst size, the DMA hangs with partial burst at the end.
Fix this by reducing the burst size to the largest power-of-2 value that evenly divides the transfer length. For example, a 40-byte transfer with a 16-byte max burst will now use an 8-byte burst (40 / 8 = 5 complete bursts) instead of causing a hang.
This issue was observed with the PL011 UART driver where TX DMA transfers of arbitrary lengths were stuck.
From the CVE record · Linux
The Linux kernel’s Tegra GPC DMA driver can hang when a transfer length is not divisible by the channel’s configured maximum burst size. This was observed with PL011 UART transmit transfers of arbitrary lengths. The input does not describe an attacker, access requirements, or user interaction.
Engineers running Linux kernels that use Tegra GPC DMA should check whether their versions are affected; no affected versions are specified.