spi: microchip-core-qspi: don't attempt to transmit during emulated read-only dual/quad operations
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 67184f361ab4d9fac6d2b8d5fed6649d496038a4, Kernel eb56deaabf127e8985fc91fa6c97bf8a3b062844 and Kernel ec9d0ddbde6003c303fa5e1d5cd48952852984d8.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.17, >=8f9cf02c8852837923f1cdacfcc92e138513325c <67184f361ab4d9fac6d2b8d5fed6649d496038a4, >=8f9cf02c8852837923f1cdacfcc92e138513325c <eb56deaabf127e8985fc91fa6c97bf8a3b062844, >=8f9cf02c8852837923f1cdacfcc92e138513325c <ec9d0ddbde6003c303fa5e1d5cd48952852984d8 | 67184f361ab4d9fac6d2b8d5fed6649d496038a4, eb56deaabf127e8985fc91fa6c97bf8a3b062844, ec9d0ddbde6003c303fa5e1d5cd48952852984d8 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket