LiveActive security incident?Get immediate response
CVE Record

CVE-2026-45996: spi: imx: fix use-after-free on unbind

In the Linux kernel, the following vulnerability has been resolved: spi: imx: fix use-after-free on unbind The SPI subsystem frees the controller and any subsystem allocated driver data as part of deregistration (unless the allocation is device managed). Take another reference before deregistering the controller so that the driver data is not freed until the driver is done with it.

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

Security readout for executives and security teams

Plain-English summary

CVE-2026-45996 is a Linux kernel flaw in the i.MX SPI driver. During device unbind, driver data can be freed before the driver is finished using it. That can create kernel memory corruption or crash risk. The public record does not provide a CVSS score or evidence of exploitation.

Executive priority

Treat as a targeted kernel maintenance issue, not a confirmed emergency. Prioritize patching for products and operational systems built on i.MX hardware because kernel memory-safety bugs can affect availability and platform integrity.

Technical view

The issue is a use-after-free in spi-imx unbind handling. The SPI subsystem may free the controller and subsystem-allocated driver data during deregistration. The fix takes another reference before deregistering the controller so driver data remains valid until cleanup completes.

Likely exposure

Exposure appears limited to Linux systems using the i.MX SPI controller driver on affected kernel builds. This is most relevant to embedded, industrial, appliance, and ARM-based platforms. The source bundle does not establish remote reachability or broad server exposure.

Exploitation context

No active exploitation is reported in the provided sources, and the CVE is not marked KEV. The vulnerable path is driver unbind/deregistration, which suggests local device-management or lifecycle activity, but the sources do not state required privileges or exploitability.

Researcher notes

The record lacks CVSS, CWE, and privilege details. Analysis should stay anchored to the unbind use-after-free fixed by reference management. Avoid assuming remote attack surface; validate actual driver presence and downstream backports.

Mitigation direction

  • Apply Linux vendor or stable kernel updates containing the referenced fixes.
  • Prioritize embedded or ARM fleets using i.MX SPI hardware.
  • Check downstream distribution advisories for fixed package versions.
  • Restrict unnecessary driver unbind or device-management access where practical.

Validation and detection

  • Inventory kernels and identify systems using the spi-imx driver.
  • Compare deployed kernel builds against vendor fixed releases or referenced commits.
  • Review logs for unexpected SPI controller unbind or kernel crash events.
  • Confirm vendor advisories before declaring non-Linux or non-i.MX systems affected.
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-45996 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
LinuxLinux307c897db762d1e0feee9477276b08f6deca4a5b, 307c897db762d1e0feee9477276b08f6deca4a5b, 307c897db762d1e0feee9477276b08f6deca4a5b, 307c897db762d1e0feee9477276b08f6deca4a5b, 307c897db762d1e0feee9477276b08f6deca4a5bunaffected
LinuxLinux5.19, 0, 6.6.140, 6.12.86, 6.18.27, 7.0.4, 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.