{"api_version":"1","generated_at":"2026-05-29T22:02:21+00:00","cve":"CVE-2026-46192","urls":{"html":"https://cve.report/CVE-2026-46192","api":"https://cve.report/api/cve/CVE-2026-46192.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-46192","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-46192"},"summary":{"title":"spi: microchip-core-qspi: don't attempt to transmit during emulated read-only dual/quad operations","description":"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.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-05-28 10:16:34","updated_at":"2026-05-28 13:44:01"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/67184f361ab4d9fac6d2b8d5fed6649d496038a4","name":"https://git.kernel.org/stable/c/67184f361ab4d9fac6d2b8d5fed6649d496038a4","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/ec9d0ddbde6003c303fa5e1d5cd48952852984d8","name":"https://git.kernel.org/stable/c/ec9d0ddbde6003c303fa5e1d5cd48952852984d8","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/eb56deaabf127e8985fc91fa6c97bf8a3b062844","name":"https://git.kernel.org/stable/c/eb56deaabf127e8985fc91fa6c97bf8a3b062844","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-46192","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46192","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 8f9cf02c8852837923f1cdacfcc92e138513325c ec9d0ddbde6003c303fa5e1d5cd48952852984d8 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 8f9cf02c8852837923f1cdacfcc92e138513325c 67184f361ab4d9fac6d2b8d5fed6649d496038a4 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 8f9cf02c8852837923f1cdacfcc92e138513325c eb56deaabf127e8985fc91fa6c97bf8a3b062844 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.17","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.17 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.30 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0.7 7.0.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1-rc3 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"46192","cve":"CVE-2026-46192","epss":"0.000170000","percentile":"0.043220000","score_date":"2026-05-28","updated_at":"2026-05-29 00:13:15"},"legacy_qids":[]},"source_records":{"cve_program":{"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'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."}],"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't 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"},"nvd":{"publishedDate":"2026-05-28 10:16:34","lastModifiedDate":"2026-05-28 13:44:01","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"46192","Ordinal":"1","Title":"spi: microchip-core-qspi: don't attempt to transmit during emula","CVE":"CVE-2026-46192","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"46192","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"spi: microchip-core-qspi: don't attempt to transmit during emula"}]}}}