CVE-2026-46192

Source
https://cve.org/CVERecord?id=CVE-2026-46192
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-46192.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-46192
Downstream
Related
Published
2026-05-28T09:36:45.770Z
Modified
2026-07-08T08:02:17.945037737Z
Summary
spi: microchip-core-qspi: don't attempt to transmit during emulated read-only dual/quad operations
Details

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.

Database specific
{
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/46xxx/CVE-2026-46192.json",
    "cna_assigner": "Linux"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
8f9cf02c8852837923f1cdacfcc92e138513325c
Fixed
ec9d0ddbde6003c303fa5e1d5cd48952852984d8
Fixed
67184f361ab4d9fac6d2b8d5fed6649d496038a4
Fixed
eb56deaabf127e8985fc91fa6c97bf8a3b062844

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-46192.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
6.17.0
Fixed
6.18.30
Type
ECOSYSTEM
Events
Introduced
6.19.0
Fixed
7.0.7

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-46192.json"