LiveActive security incident?Get immediate response
CVE Record

CVE-2026-46225: spi: rspi: fix controller deregistration

In the Linux kernel, the following vulnerability has been resolved: spi: rspi: fix controller deregistration Make sure to deregister the controller before releasing underlying resources like DMA during driver unbind.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

A Linux kernel SPI driver unbind path released resources in the wrong order. On systems using the RSPI controller driver, this could create stability or safety risk during driver removal. The public sources do not provide CVSS, impact detail, or exploitation evidence.

Executive priority

Track and remediate through normal kernel maintenance unless the organization operates RSPI-based embedded platforms. Escalate priority for systems where driver unbind, hotplug, or field reliability is safety-critical.

Technical view

The issue is in the Linux kernel RSPI SPI controller driver. The fix deregisters the SPI controller before releasing underlying resources such as DMA during driver unbind. This is an operational lifetime-ordering bug, with details limited to the kernel CVE text and stable commit references.

Likely exposure

Exposure appears limited to Linux systems that include and use the RSPI SPI controller driver on relevant hardware. General-purpose systems without this driver or hardware are less likely exposed, but source data does not provide product-level mapping.

Exploitation context

No cited source states active exploitation, and the CVE is not marked KEV. The bundle does not include exploit prerequisites, impact class, or proof-of-concept details, so exploitability should be treated as unconfirmed.

Researcher notes

The record lacks CVSS, CWE, and impact details. Analysis should focus on driver lifetime ordering during unbind and whether downstream kernels include the stable commits. Do not assume remote exploitation or broad kernel compromise from available evidence.

Mitigation direction

  • Identify kernels using the RSPI SPI controller driver.
  • Apply the relevant Linux stable update containing the referenced fix.
  • Check vendor kernel advisories for backported patches.
  • Prioritize embedded or hardware platforms using RSPI.
  • Avoid direct wrangler-style deployment assumptions; follow vendor update process.

Validation and detection

  • Inventory running kernel versions and downstream vendor builds.
  • Confirm whether RSPI driver support is built or loaded.
  • Map installed kernels against vendor fixed releases or referenced commits.
  • Review unbind, DMA, or SPI controller errors in system logs.
  • Validate updates in hardware-specific test environments before production rollout.
Prepared
Confidence
medium
Sources
7

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-46225 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
6Source 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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux9e03d05eee4ca45ed12749ef6c26bf616262cdd2, 9e03d05eee4ca45ed12749ef6c26bf616262cdd2, 9e03d05eee4ca45ed12749ef6c26bf616262cdd2, 9e03d05eee4ca45ed12749ef6c26bf616262cdd2, 9e03d05eee4ca45ed12749ef6c26bf616262cdd2unaffected
LinuxLinux3.14, 0, 6.6.140, 6.12.90, 6.18.32, 7.0.9, 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.