spi: microchip-core-qspi: don't attempt to transmit during emulated read-only dual/quad operations
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 |
|
|
6.18.307.0.77.1In the Linux kernel, the following vulnerability has been resolved:
spi: microchip-core-qspi: don't attempt to transmit during emulated read-only dual/quad operations
The core will deal with reads by creating clock cycles itself, there's no need to generate clock cycles by transmitting garbage data at the driver level. Further, transmitting garbage data just bricks the transfer since QSPI doesn't have a dedicated master-out line like MOSI in regular SPI. I'm not entirely sure if the transfer is bricked because of the garbage data being transmitted on the bus or because the core loses track of whether it is supposed to be sending or receiving data.
From the CVE record · Linux
The Linux kernel's microchip-core-qspi driver attempts to transmit data during emulated read-only dual/quad operations, which can break the transfer. The input does not establish whether an attacker can trigger this behavior or specify any network, authentication, or user-interaction conditions.
Engineers running Linux kernels that use the microchip-core-qspi driver should check their versions; affected versions were not provided.