LiveActive security incident?Get immediate response
CVE Record

CVE-2026-46226: spi: fsl: fix controller deregistration

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

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects the fsl SPI driver during driver unbind. The bug is in cleanup ordering: resources such as DMA could be released before the SPI controller is deregistered. Business risk is unclear because no severity score, CWE, or exploitation evidence is provided.

Executive priority

Treat as a patch-tracking kernel issue, not an emergency based on current evidence. Escalate priority for embedded or operational systems that use the fsl SPI driver, because kernel driver cleanup bugs can affect system stability.

Technical view

CVE-2026-46226 resolves a Linux kernel fsl SPI controller deregistration flaw. The fix changes teardown order so the SPI controller is deregistered before underlying resources, including DMA, are released during driver unbind. The provided sources do not describe impact primitives, attacker requirements, or affected distributions.

Likely exposure

Exposure is most likely on Linux systems using the fsl SPI driver and vulnerable kernel versions. This is especially relevant where driver unbind can occur. The provided sources do not identify specific distributions, appliances, cloud images, or hardware models.

Exploitation context

The source bundle shows KEV is false and provides no cited evidence of active exploitation. The available description indicates a driver cleanup bug triggered during unbind, but does not establish remote reachability, privilege requirements, or exploitability.

Researcher notes

The evidence is limited to the CVE description and stable kernel commit references. No CVSS, CWE, exploit status, attack vector, or distribution-specific fixed versions are included. Validation should focus on code lineage and whether fsl SPI driver unbind is reachable in the environment.

Mitigation direction

  • Update to a vendor or distro kernel containing the referenced stable fixes.
  • Check Linux distributor advisories for supported fixed package versions.
  • Prioritize systems using the fsl SPI driver or driver unbind workflows.
  • Reboot into the fixed kernel after applying kernel updates.
  • If no fixed package exists, monitor vendor guidance rather than inventing workarounds.

Validation and detection

  • Inventory Linux kernel versions across affected systems.
  • Identify systems loading or packaging the fsl SPI driver.
  • Compare kernel changelogs against the referenced stable commit IDs.
  • Confirm patched systems booted into the updated kernel.
  • Review recent kernel logs for SPI driver unbind or teardown failures.
Prepared
Confidence
medium
Sources
7

Public sources used

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-46226 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4178b6b1b595003cd6e04711b449797a582e44f5, 4178b6b1b595003cd6e04711b449797a582e44f5, 4178b6b1b595003cd6e04711b449797a582e44f5, 4178b6b1b595003cd6e04711b449797a582e44f5, 4178b6b1b595003cd6e04711b449797a582e44f5unaffected
LinuxLinux4.3, 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.