spi: microchip-core: ensure TX and RX FIFOs are empty at start of a transfer
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: microchip-core: ensure TX and RX FIFOs are empty at start of a transfer
While transmitting with rx_len == 0, the RX FIFO is not going to be emptied in the interrupt handler. A subsequent transfer could then read crap from the previous transfer out of the RX FIFO into the start RX buffer. The core provides a register that will empty the RX and TX FIFOs, so do that before each transfer.
From the CVE record · Linux
The Linux kernel microchip-core SPI driver can leave data in the RX FIFO when a transfer has rx_len == 0. A subsequent transfer may read that stale data into the start of its RX buffer. The input does not establish an attacker path or specify authentication or user-interaction requirements.
Engineers running Linux kernels with the microchip-core SPI driver should check their deployments; affected versions are not specified.