CVE-2026-46192
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
| OS | Version | Status | Fixed in |
|---|---|---|---|
| debian | bookworm | fixed | 0 |
| debian | bullseye | fixed | 0 |
| debian | forky | fixed | 7.0.7-1 |
| debian | sid | fixed | 7.0.7-1 |
| debian | trixie | fixed | 0 |
| sles | affected | |
References
- https://git.kernel.org/stable/c/67184f361ab4d9fac6d2b8d5fed6649d496038a4
- https://git.kernel.org/stable/c/eb56deaabf127e8985fc91fa6c97bf8a3b062844
- https://git.kernel.org/stable/c/ec9d0ddbde6003c303fa5e1d5cd48952852984d8
- https://security-tracker.debian.org/tracker/CVE-2026-46192
- https://www.suse.com/security/cve/CVE-2026-46192.html
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.