Description
In 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.
Product status
8f9cf02c8852837923f1cdacfcc92e138513325c (git) before ec9d0ddbde6003c303fa5e1d5cd48952852984d8
8f9cf02c8852837923f1cdacfcc92e138513325c (git) before 67184f361ab4d9fac6d2b8d5fed6649d496038a4
8f9cf02c8852837923f1cdacfcc92e138513325c (git) before eb56deaabf127e8985fc91fa6c97bf8a3b062844
6.17
Any version before 6.17
6.18.30 (semver)
7.0.7 (semver)
7.1-rc3 (original_commit_for_fix)
References
git.kernel.org/...c/ec9d0ddbde6003c303fa5e1d5cd48952852984d8
git.kernel.org/...c/67184f361ab4d9fac6d2b8d5fed6649d496038a4
git.kernel.org/...c/eb56deaabf127e8985fc91fa6c97bf8a3b062844