{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-46192", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "state": "PUBLISHED", "assignerShortName": "Linux", "dateReserved": "2026-05-13T15:03:33.104Z", "datePublished": "2026-05-28T09:36:45.770Z", "dateUpdated": "2026-05-28T09:36:45.770Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-05-28T09:36:45.770Z"}, "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nspi: microchip-core-qspi: don't attempt to transmit during emulated read-only dual/quad operations\n\nThe core will deal with reads by creating clock cycles itself, there's\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't have a dedicated master-out line like MOSI in regular\nSPI. I'm 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."}], "affected": [{"product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["drivers/spi/spi-microchip-core-qspi.c"], "versions": [{"version": "8f9cf02c8852837923f1cdacfcc92e138513325c", "lessThan": "ec9d0ddbde6003c303fa5e1d5cd48952852984d8", "status": "affected", "versionType": "git"}, {"version": "8f9cf02c8852837923f1cdacfcc92e138513325c", "lessThan": "67184f361ab4d9fac6d2b8d5fed6649d496038a4", "status": "affected", "versionType": "git"}, {"version": "8f9cf02c8852837923f1cdacfcc92e138513325c", "lessThan": "eb56deaabf127e8985fc91fa6c97bf8a3b062844", "status": "affected", "versionType": "git"}]}, {"product": "Linux", "vendor": "Linux", "defaultStatus": "affected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["drivers/spi/spi-microchip-core-qspi.c"], "versions": [{"version": "6.17", "status": "affected"}, {"version": "0", "lessThan": "6.17", "status": "unaffected", "versionType": "semver"}, {"version": "6.18.30", "lessThanOrEqual": "6.18.*", "status": "unaffected", "versionType": "semver"}, {"version": "7.0.7", "lessThanOrEqual": "7.0.*", "status": "unaffected", "versionType": "semver"}, {"version": "7.1-rc3", "lessThanOrEqual": "*", "status": "unaffected", "versionType": "original_commit_for_fix"}]}], "cpeApplicability": [{"nodes": [{"operator": "OR", "negate": false, "cpeMatch": [{"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.17", "versionEndExcluding": "6.18.30"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.17", "versionEndExcluding": "7.0.7"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.17", "versionEndExcluding": "7.1-rc3"}]}]}], "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't attempt to transmit during emulated read-only dual/quad operations", "x_generator": {"engine": "bippy-1.2.0"}}}}

{}

{"cveTags": [], "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nspi: microchip-core-qspi: don't attempt to transmit during emulated read-only dual/quad operations\n\nThe core will deal with reads by creating clock cycles itself, there's\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't have a dedicated master-out line like MOSI in regular\nSPI. I'm 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": "CVE-2026-46192", "lastModified": "2026-05-28T10:16:34.837", "metrics": {}, "published": "2026-05-28T10:16:34.837", "references": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/67184f361ab4d9fac6d2b8d5fed6649d496038a4"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/eb56deaabf127e8985fc91fa6c97bf8a3b062844"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/ec9d0ddbde6003c303fa5e1d5cd48952852984d8"}], "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "vulnStatus": "Received"}

{}

{}