spi: don't unoptimize message in spi_async()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
spi: don't unoptimize message in spi_async()
Calling spi_maybe_unoptimize_message() in spi_async() is wrong because the message is likely to be in the queue and not transferred yet. This can corrupt the message while it is being used by the controller driver.
spi_maybe_unoptimize_message() is already called in the correct place in spi_finalize_current_message() to balance the call to spi_maybe_optimize_message() in spi_async().
From the CVE record · Linux
The Linux kernel’s SPI async path can unoptimize a queued message before the controller driver finishes using it, potentially corrupting the message. The input does not specify an attack route, authentication requirements, or user-interaction requirements.
Engineers running Linux kernels with the affected SPI code should check their versions; affected versions are not specified in the input.