CVE-2026-46192: spi: microchip-core-qspi: don't attempt to transmit during emulated read-only dual/quad operations
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 Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Modify the microchip-core-qspi driver so it does not attempt to transmit garbage data during emulated read-only dual/quad read operations; rely on the SPI core to generate clock cycles for reads.
Linux kernel (spi: microchip-core-qspi driver) emulated read-only dual/quad transmit behavior = do not attempt to transmit during emulated read-only dual/quad operations
Event History
Frequently Asked Questions
What is the severity of CVE-2026-46192?
The severity of CVE-2026-46192 is rated at 11.
How do I fix CVE-2026-46192?
To fix CVE-2026-46192, update the Linux kernel to the latest version where the vulnerability is addressed.
What systems are affected by CVE-2026-46192?
CVE-2026-46192 affects the Linux kernel, specifically microchip-core-qspi implementations.
What type of vulnerability is CVE-2026-46192?
CVE-2026-46192 is categorized as an issue related to improper handling of emulated read-only dual/quad operations.
What impact does CVE-2026-46192 have on system performance?
CVE-2026-46192 could lead to unnecessary clock cycles being generated, possibly impacting system efficiency.