Bug 2482601 (CVE-2026-46192) - CVE-2026-46192 kernel: spi: microchip-core-qspi: don't attempt to transmit during emulated read-only dual/quad operations
Summary: CVE-2026-46192 kernel: spi: microchip-core-qspi: don't attempt to transmit du...
Keywords:
Status: NEW
Alias: CVE-2026-46192
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-05-28 11:05 UTC by OSIDB Bzimport
Modified: 2026-05-28 14:04 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-05-28 11:05:16 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.