LiveActive security incident?Get immediate response
CVE Record

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel driver flaw affecting Microchip Core QSPI read operations. In specific dual/quad read paths, the driver sends junk data when it should only clock reads, which can break the transfer. Available evidence points to device I/O reliability risk, not broad remote compromise.

Executive priority

Treat as targeted operational risk for affected embedded Linux platforms, not an internet-scale emergency. Prioritize if QSPI storage or peripherals support business-critical boot, firmware, or data paths.

Technical view

The microchip-core-qspi SPI driver attempted transmission during emulated read-only dual/quad operations. The kernel core can generate required clock cycles; driver-level dummy transmit may brick the QSPI transfer because QSPI lacks a dedicated MOSI line. Kernel stable commits resolve this behavior. No CVSS, CWE, or privilege-boundary impact is provided.

Likely exposure

Likely limited to Linux systems using the Microchip Core QSPI driver and affected kernel builds. The source bundle lists Linux versions and commit identifiers, but does not clearly define affected version ranges or downstream distribution status.

Exploitation context

No active exploitation is cited, and the CVE is not marked KEV. The provided text describes a driver logic flaw during QSPI transfers, with no public exploit status, attacker prerequisites, or security impact details beyond broken transfers.

Researcher notes

Evidence is sparse: no CVSS, CWE, exploitability analysis, or clarified version ranges are provided. Analysis should stay focused on the QSPI driver behavior and the three kernel stable references.

Mitigation direction

  • Check vendor or distribution kernel advisories for CVE-2026-46192 coverage.
  • Update to a kernel build containing the referenced stable fixes.
  • Prioritize embedded or SoC systems using Microchip Core QSPI hardware.
  • If updates are unavailable, ask the vendor for supported mitigation guidance.

Validation and detection

  • Inventory systems for Linux kernels using the microchip-core-qspi driver.
  • Compare kernel source or package changelogs against the referenced stable commits.
  • Confirm affected devices exercise dual or quad QSPI read operations.
  • Monitor boot, flash, or peripheral I/O logs for QSPI transfer failures.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-46192 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux8f9cf02c8852837923f1cdacfcc92e138513325c, 8f9cf02c8852837923f1cdacfcc92e138513325c, 8f9cf02c8852837923f1cdacfcc92e138513325cunaffected
LinuxLinux6.17, 0, 6.18.30, 7.0.7, 7.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.