CVE-2026-46148

Description

In the Linux kernel, the following vulnerability has been resolved: spi: microchip-core-qspi: control built-in cs manually The coreQSPI IP supports only a single chip select, which is automagically operated by the hardware - set low when the transmit buffer first gets written to and set high when the number of bytes written to the TOTALBYTES field of the FRAMES register have been sent on the bus. Additional devices must use GPIOs for their chip selects. It was reported to me that if there are two devices attached to this QSPI controller that the in-built chip select is set low while linux tries to access the device attached to the GPIO. This went undetected as the boards that connected multiple devices to the SPI controller all exclusively used GPIOs for chip selects, not relying on the built-in chip select at all. It turns out that this was because the built-in chip select, when controlled automagically, is set low when active and high when inactive, thereby ruling out its use for active-high devices or devices that need to transmit with the chip select disabled. Modify the driver so that it controls chip select directly, retaining the behaviour for mem_ops of setting the chip select active for the entire duration of the transfer in the exec_op callback. For regular transfers, implement the set_cs callback for the core to use. As part of this, the existing setup callback, mchp_coreqspi_setup_op(), is removed. Modifying the CLKIDLE field is not safe to do during operation when there are multiple devices, so this code is removed entirely. Setting the MASTER and ENABLE fields is something that can be done once at probe, it doesn't need to be re-run for each device. Instead the new setup callback sets the built-in chip select to its inactive state for active-low devices, as the reset value of the chip select in software controlled mode is low.

Overview

State: PUBLISHED
Assigner (CNA): Linux
CVSS severity: high
CVSS score: 7.3 / 10
CVSS vector: AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Effective score: 7.3 / 10 HIGH source: CNA overview
MSRC score: 5.5 / 10 MEDIUM MS rating: Moderate
CWE(s): —
Reserved: 2026-05-13
Published: 2026-05-28 09:36 UTC
Last updated: 2026-05-28 09:36 UTC
Source: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/46xxx/CVE-2026-46148.json
Linked Threat: CVE-2026-46148 — CVE-2026-46148

NVD triage scoring NVD CVE 2.0

Layer NVD adds on top of the CNA's CVE record — published / last-modified timestamps, exploitability / impact subscores, and the FIRST.org EPSS probability that this CVE will be exploited in the wild in the next 30 days.

NVD published: 2026-05-28 10:16:30 UTC
NVD last modified: 2026-06-17 10:53:09 UTC
NVD CVSS v3.1: 5.5 / 10 MEDIUM source: nvd@nist.gov
NVD CVSS vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Exploitability subscore: 1.8 / 10
Impact subscore: 3.6 / 10
EPSS score: 0.0012 (probability of exploitation in next 30 days)
EPSS percentile: 2.21% vs all CVEs — higher = more likely to be exploited, as of 2026-07-27

European Union Vulnerability Database ENISA EUVD

ENISA's official EU repository for curated vulnerability intelligence. Carries a separate identifier (EUVD-YYYY-NNNN) and frequently exposes an earlier-published description + CVSS than NVD does.

EUVD ID: EUVD-2026-32775
Assigner: Linux
Published: May 28, 2026, 9:36:04 AM
Updated: Jun 14, 2026, 5:58:05 PM
EUVD base score: 0.0 / 10
EUVD-reported EPSS: 0.1200
Vendors: Linux
Products: Linux (8596124c4c1bc7561454cee0463c16eca70b5d25 <998f43196d732f20f9b71eb6ebd973736c9fa911)

Linux (patch: 7.1)

Linux (8596124c4c1bc7561454cee0463c16eca70b5d25 <ee3c99aa102212ad59dc2c19595515c4a6729307)

Linux (patch: 6.18.30)

Linux (6.1)

Linux (8596124c4c1bc7561454cee0463c16eca70b5d25 <7672749e1496215e8683ce57cf323119033954cf)

Linux (patch: 0)

Linux (patch: 7.0.7)
Aliases: GHSA-v9m3-f9j3-xrv6

ENISA description: In the Linux kernel, the following vulnerability has been resolved: spi: microchip-core-qspi: control built-in cs manually The coreQSPI IP supports only a single chip select, which is automagically operated by the hardware - set low when the transmit buffer first gets written to and set high when the number of bytes written to the TOTALBYTES field of the FRAMES register have been sent on the bus. Additional devices must use GPIOs for their chip selects. It was reported to me that if there are two devices attached to this QSPI controller that the in-built chip select is set low while linux tries to access the device attached to the GPIO. This went undetected as the boards that connected multiple devices to the SPI controller all exclusively used GPIOs for chip selects, not relying on the built-in chip select at all. It turns out that this was because the built-in chip select, when controlled automagically, is set low when active and high when inactive, thereby ruling out its use for active-high devices or devices that need to transmit with the chip select disabled. Modify the driver so that it controls chip select directly, retaining the behaviour for mem_ops of setting the chip select active for the entire duration of the transfer in the exec_op callback. For regular transfers, implement the set_cs callback for the core to use. As part of this, the existing setup callback, mchp_coreqspi_setup_op(), is removed. Modifying the CLKIDLE field is not safe to do during operation when there are multiple devices, so this code is removed entirely. Setting the MASTER and ENABLE fields is something that can be done once at probe, it doesn't need to be re-run for each device. Instead the new setup callback sets the built-in chip select to its inactive state for active-low devices, as the reset value of the chip select in software controlled mode is low.

EUVD references (3)

Microsoft Security Response Center MSRC

Microsoft's vendor-authoritative record from the Security Update Guide — its own CVSS score, impact, severity rating, exploit assessment, and KB-article fixes. Refreshed 2026-11-05 03:38 UTC (source: CVRF).

MS severity: Moderate
MS CVSS base score: 5.5 / 10 (temporal 5.1)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H/E:U
Release: 2026-May

Affected products (2)

Vendor	Product	Versions	Platforms
Linux	Linux	`8596124c4c1bc7561454cee0463c16eca70b5d25` (affected), `8596124c4c1bc7561454cee0463c16eca70b5d25` (affected), `8596124c4c1bc7561454cee0463c16eca70b5d25` (affected)	—
Linux	Linux	`6.1` (affected), `0` (unaffected), `6.18.30` (unaffected), `7.0.7` (unaffected), `7.1-rc3` (unaffected)	—

Affected products — CPE 2.3 (3) NVD

NVD's normalized CPE 2.3 matchers, used by vendor tools (vulnerability scanners, asset managers) for automated detection. Compare with the CNA's free-text "Affected products" section above.

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:*

Vendor references (3)

References embedded in the original CVE record by the assigning CNA.

Web references (7)

DuckDuckGo results ranked by threat-intel / vendor advisory domains. Generated by the 🔎 Find references (web) button above — same flow as the Remediations search.

MSRC update guide: CVE-2026-46148 msrc
https://git.kernel.org/stable/c/998f43196d732f20f9b71eb6ebd973736c9fa911 tenable:git.kernel.org
https://git.kernel.org/stable/c/ee3c99aa102212ad59dc2c19595515c4a6729307 tenable:git.kernel.org
https://git.kernel.org/stable/c/7672749e1496215e8683ce57cf323119033954cf tenable:git.kernel.org
https://nvd.nist.gov/vuln/detail/CVE-2026-46148 tenable:nvd.nist.gov
https://www.cve.org/CVERecord?id=CVE-2026-46148 tenable:www.cve.org
https://www.first.org/epss/ tenable:www.first.org

NVD-tagged references (3)

Reference list NVD curates from the CNA record, vendor advisories, and third-party reports. The tag chips below are NVD's analyst-assigned categories.

https://git.kernel.org/stable/c/7672749e1496215e8683ce57cf323119033954cf 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Patch
https://git.kernel.org/stable/c/998f43196d732f20f9b71eb6ebd973736c9fa911 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Patch
https://git.kernel.org/stable/c/ee3c99aa102212ad59dc2c19595515c4a6729307 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Patch

Remediations (20)

Remediations are stored against the linked Threat row; the list below is deduplicated across both pages.

Security Updates - Red Hat Customer Portal

web:access.redhat.com

Learn about our open source products, services, and company. You are here

2026-06-04 00:00 UTC
Oracle Critical Patch Update, April 2026 Security Update Review

web:blog.qualys.com

Oracle released its second quarterly edition of this year's Critical Patch Update. The update received patches for 481 security vulnerabilities.

2026-06-04 00:00 UTC
Oracle Releases Critical Security Patch Fixing 337 Vulnerabilities ...

web:cyberpress.org

Oracle has released its January 2026 Critical Patch Update (CPU), delivering security patches for 337 vulnerabilities across multiple product families. Published through Oracle's Security Alerts portal, the advisory emphasizes the cumulative nature of these patches and strongly recommends immediate deployment across enterprise environments to ...

2026-06-04 00:00 UTC
Microsoft Patch Tuesday May 2026 - 120 Vulnerabilities Fixed, Including ...

web:cybersecuritynews.com

Microsoft's May 2026 Patch Tuesday lands with a heavy enterprise focus, fixing 120 vulnerabilities across Windows, Office, Azure, developer tools, and Microsoft 365 apps, including 29 remote code execution (RCE) flaws rated Critical.

2026-06-04 00:00 UTC
Security Update Guide - Microsoft

web:portal.msrc.microsoft.com

The Security Update Guide provides information on the latest Microsoft security updates, helping users understand and address potential vulnerabilities effectively.

2026-06-04 00:00 UTC
Landing Page | ServiceNow Common Vulnerabilities & Exposures (CVE ...

web:support.servicenow.com

Overview The advisories below document publicly disclosed Common Vulnerabilities and Exposures ( CVEs ) in the Now Platform by ServiceNow. Because ServiceNow uses various methods to communicate vulnerability information, patches, and other fixes, customers should review family, security patch , and hotfix release notes, which are available at https://docs.servicenow.com, for a complete list of ...

2026-06-04 00:00 UTC
April 2026 Patch Tuesday: Updates and Analysis | CrowdStrike

web:www.crowdstrike.com

Microsoft's April 2026 Patch Tuesday addresses 164 CVEs , featuring 8 Critical vulnerabilities, one exploited zero-day, and one disclosed zero-day.

2026-06-04 00:00 UTC
Oracle Critical Security Patch Update Advisory - May 2026

web:www.oracle.com

This Critical Security Patch Update contains 35 new security patches across the product families listed below. Please note that an MOS note summarizing the content of this Critical Security Patch Update and other Oracle Software Security Assurance activities is located at May 2026 Critical Security Patch Update: Executive Summary and Analysis.

2026-06-04 00:00 UTC
VirusTotal - Home

web:www.virustotal.com

VirusTotal is a platform for scanning files and URLs for viruses, malware, and other threats using multiple antivirus engines.

2026-06-04 00:00 UTC
Patch Tuesday June 2026: Security Updates & CVE Analysis

web:zecurit.com

Get the complete breakdown of Microsoft's June 2026 Patch Tuesday. We analyze the latest security updates and all critical CVEs .

2026-06-04 00:00 UTC
Microsoft®Update Catalog

web:catalog.update.microsoft.com

Welcome to the Microsoft Update Catalog site. We want your feedback! Visit our newsgroup or send us an email to provide us with your thoughts and suggestions. To get started using the site, enter in your search terms in the Search box above or visit our FAQ for search tips. |Newsgroup|Send us your feedback Accessibilité : partiellement conforme

2026-06-19 02:28 UTC
Game Update Notes: May 12, 2026 - Guild Wars 2 Forums

web:en-forum.guildwars2.com

05/12/2026—May 12 Release Notes Note to users of third-party programs: The game may not launch or work properly after we release a new build if you use a third-party program, due to possible incompatibilities. ArenaNet cannot offer support if a third-party modification breaks, interferes with, or ...

2026-06-19 02:28 UTC
Google Gemini

web:gemini.google.com

Get assistance with writing, planning, learning, and more from Google AI.

2026-06-19 02:28 UTC
MitigationPlanningPortal - FEMA

web:hazards.fema.gov

Access the FEMA Mitigation Planning Portal to manage and update your mitigation plans securely.

2026-06-19 02:28 UTC
Security Update Guide - Microsoft Security Response Center

web:msrc.microsoft.com

Security Update Guide - Microsoft Security Response Center

2026-06-19 02:28 UTC
OnlyFans

web:onlyfans.com

OnlyFans is the social platform revolutionizing creator and fan connections. The site is inclusive of artists and content creators from all genres and allows them to monetize their content while developing authentic relationships with their fanbase.

2026-06-19 02:28 UTC
WhatsApp Web

web:web.whatsapp.com

Log in to WhatsApp Web for simple, reliable and private messaging on your desktop. Send and receive messages and files with ease, all for free.

2026-06-19 02:28 UTC
Grammarly: Free AI Writing Assistance

web:www.grammarly.com

Grammarly makes AI writing convenient. Work smarter with personalized AI guidance and text generation on any app or website.

2026-06-19 02:28 UTC
What's Happening with the Estrogen Patch Shortage in the U.S.?

web:www.womenshealthmag.com

An estrogen patch shortage in the U.S. is disrupting menopause care, but doctors stress that there are other options for women.

2026-06-19 02:28 UTC

AI Forensic Analysis

Only Available for Registered Users. Sign in to view.

Raw JSON

The full cvelistV5 record. Download as CVE-2026-46148.json.

{
  "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": "998f43196d732f20f9b71eb6ebd973736c9fa911",
              "status": "affected",
              "version": "8596124c4c1bc7561454cee0463c16eca70b5d25",
              "versionType": "git"
            },
            {
              "lessThan": "ee3c99aa102212ad59dc2c19595515c4a6729307",
              "status": "affected",
              "version": "8596124c4c1bc7561454cee0463c16eca70b5d25",
              "versionType": "git"
            },
            {
              "lessThan": "7672749e1496215e8683ce57cf323119033954cf",
              "status": "affected",
              "version": "8596124c4c1bc7561454cee0463c16eca70b5d25",
              "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.1"
            },
            {
              "lessThan": "6.1",
              "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.1",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.0.7",
                  "versionStartIncluding": "6.1",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1-rc3",
                  "versionStartIncluding": "6.1",
                  "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: control built-in cs manually\n\nThe coreQSPI IP supports only a single chip select, which is\nautomagically operated by the hardware - set low when the transmit\nbuffer first gets written to and set high when the number of bytes\nwritten to the TOTALBYTES field of the FRAMES register have been sent on\nthe bus. Additional devices must use GPIOs for their chip selects.\nIt was reported to me that if there are two devices attached to this\nQSPI controller that the in-built chip select is set low while linux\ntries to access the device attached to the GPIO.\n\nThis went undetected as the boards that connected multiple devices to\nthe SPI controller all exclusively used GPIOs for chip selects, not\nrelying on the built-in chip select at all. It turns out that this was\nbecause the built-in chip select, when controlled automagically, is set\nlow when active and high when inactive, thereby ruling out its use for\nactive-high devices or devices that need to transmit with the chip\nselect disabled.\n\nModify the driver so that it controls chip select directly, retaining\nthe behaviour for mem_ops of setting the chip select active for the\nentire duration of the transfer in the exec_op callback. For regular\ntransfers, implement the set_cs callback for the core to use.\n\nAs part of this, the existing setup callback, mchp_coreqspi_setup_op(),\nis removed. Modifying the CLKIDLE field is not safe to do during\noperation when there are multiple devices, so this code is removed\nentirely. Setting the MASTER and ENABLE fields is something that can be\ndone once at probe, it doesn't need to be re-run for each device.\nInstead the new setup callback sets the built-in chip select to its\ninactive state for active-low devices, as the reset value of the chip\nselect in software controlled mode is low."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-05-28T09:36:04.805Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/998f43196d732f20f9b71eb6ebd973736c9fa911"
        },
        {
          "url": "https://git.kernel.org/stable/c/ee3c99aa102212ad59dc2c19595515c4a6729307"
        },
        {
          "url": "https://git.kernel.org/stable/c/7672749e1496215e8683ce57cf323119033954cf"
        }
      ],
      "title": "spi: microchip-core-qspi: control built-in cs manually",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-46148",
    "datePublished": "2026-05-28T09:36:04.805Z",
    "dateReserved": "2026-05-13T15:03:33.101Z",
    "dateUpdated": "2026-05-28T09:36:04.805Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}