Vulnerability-Lookup

GHSA-FG62-M4W4-QG3P

Vulnerability from github – Published: 2026-05-28 12:30 – Updated: 2026-05-28 12:30

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.

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-46192"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-05-28T10:16:34Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nspi: microchip-core-qspi: don\u0027t attempt to transmit during emulated read-only dual/quad operations\n\nThe core will deal with reads by creating clock cycles itself, there\u0027s\nno need to generate clock cycles by transmitting garbage data at the\ndriver level. Further, transmitting garbage data just bricks the transfer\nsince QSPI doesn\u0027t have a dedicated master-out line like MOSI in regular\nSPI. I\u0027m not entirely sure if the transfer is bricked because of the\ngarbage data being transmitted on the bus or because the core loses\ntrack of whether it is supposed to be sending or receiving data.",
  "id": "GHSA-fg62-m4w4-qg3p",
  "modified": "2026-05-28T12:30:32Z",
  "published": "2026-05-28T12:30:32Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-46192"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/67184f361ab4d9fac6d2b8d5fed6649d496038a4"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/eb56deaabf127e8985fc91fa6c97bf8a3b062844"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/ec9d0ddbde6003c303fa5e1d5cd48952852984d8"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

CVE-2026-46192 (GCVE-0-2026-46192)

Vulnerability from cvelistv5 – Published: 2026-05-28 09:36 – Updated: 2026-05-28 09:36

Title

spi: microchip-core-qspi: don't attempt to transmit during emulated read-only dual/quad operations

Summary

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.

Severity

No CVSS data available.

Assigner

Linux

References

3 references

URL	Tags
https://git.kernel.org/stable/c/ec9d0ddbde6003c30…
https://git.kernel.org/stable/c/67184f361ab4d9fac…
https://git.kernel.org/stable/c/eb56deaabf127e898…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: 8f9cf02c8852837923f1cdacfcc92e138513325c , < ec9d0ddbde6003c303fa5e1d5cd48952852984d8 (git) Affected: 8f9cf02c8852837923f1cdacfcc92e138513325c , < 67184f361ab4d9fac6d2b8d5fed6649d496038a4 (git) Affected: 8f9cf02c8852837923f1cdacfcc92e138513325c , < eb56deaabf127e8985fc91fa6c97bf8a3b062844 (git)
Linux	Linux	Affected: 6.17 Unaffected: 0 , < 6.17 (semver) Unaffected: 6.18.30 , ≤ 6.18.* (semver) Unaffected: 7.0.7 , ≤ 7.0.* (semver) Unaffected: 7.1-rc3 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/spi/spi-microchip-core-qspi.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "ec9d0ddbde6003c303fa5e1d5cd48952852984d8",
              "status": "affected",
              "version": "8f9cf02c8852837923f1cdacfcc92e138513325c",
              "versionType": "git"
            },
            {
              "lessThan": "67184f361ab4d9fac6d2b8d5fed6649d496038a4",
              "status": "affected",
              "version": "8f9cf02c8852837923f1cdacfcc92e138513325c",
              "versionType": "git"
            },
            {
              "lessThan": "eb56deaabf127e8985fc91fa6c97bf8a3b062844",
              "status": "affected",
              "version": "8f9cf02c8852837923f1cdacfcc92e138513325c",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/spi/spi-microchip-core-qspi.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.17"
            },
            {
              "lessThan": "6.17",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.30",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.0.*",
              "status": "unaffected",
              "version": "7.0.7",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.1-rc3",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.30",
                  "versionStartIncluding": "6.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.0.7",
                  "versionStartIncluding": "6.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1-rc3",
                  "versionStartIncluding": "6.17",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nspi: microchip-core-qspi: don\u0027t attempt to transmit during emulated read-only dual/quad operations\n\nThe core will deal with reads by creating clock cycles itself, there\u0027s\nno need to generate clock cycles by transmitting garbage data at the\ndriver level. Further, transmitting garbage data just bricks the transfer\nsince QSPI doesn\u0027t have a dedicated master-out line like MOSI in regular\nSPI. I\u0027m not entirely sure if the transfer is bricked because of the\ngarbage data being transmitted on the bus or because the core loses\ntrack of whether it is supposed to be sending or receiving data."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-05-28T09:36:45.770Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/ec9d0ddbde6003c303fa5e1d5cd48952852984d8"
        },
        {
          "url": "https://git.kernel.org/stable/c/67184f361ab4d9fac6d2b8d5fed6649d496038a4"
        },
        {
          "url": "https://git.kernel.org/stable/c/eb56deaabf127e8985fc91fa6c97bf8a3b062844"
        }
      ],
      "title": "spi: microchip-core-qspi: don\u0027t attempt to transmit during emulated read-only dual/quad operations",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-46192",
    "datePublished": "2026-05-28T09:36:45.770Z",
    "dateReserved": "2026-05-13T15:03:33.104Z",
    "dateUpdated": "2026-05-28T09:36:45.770Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Detection rules are retrieved from Rulezet.

Action not permitted

GHSA-FG62-M4W4-QG3P

CVE-2026-46192 (GCVE-0-2026-46192)

Tags

Sightings

Nomenclature